Search results

in fact - none of the available languages ist the worst ever - it's just a matter of using it in the right way as well as for the right purpose....

just an update: today looks better but not perfect...... i'll try to catch after each block if there is still a transaction active and write it into a log-file maybe i'll get the answer for the my riddle....

i'm not quite sure if there is a specific function for that - if it isn't so here would be a souluten that works: use a for each - order by this value descending. seperate the last char - check if it is numeric - if not skip to next record..... might help regards cugar

okay got the listening file.... WOW what the hell is that.... using those smart-windows causes really a lot of blocks..... :confused: example: File Name Line Blk. Type Tran Blk. Label -------------------- ---- --------- ----...

okay great thanks - i'll tell you about the results...... btw.: i'll need to connect the progress-db with a c# coded software. afaik the odbc-connector not uses all possibilities of the db and the performance is pretty poor - any 3rd party products or other suggestions? thank you for...

well it is allready possible to say that the ammount of locks has decreased (just defined a do transaction on clicking the button and releasing the widget-pool...) i'm not quite shure if this is the solution - but it looks like it has to do something with that... listening-option of...

are your running kasperky-antivir - i had nearly the same problem with that....

well it looks like that the progress-client is crashing or restarting (like pressing ctrl+pause)

even when the widget pool is created a 100 times with no deletion?

yes indeed i'm used to code with "usual" SQL-Based Transaction-handling and error-handling. I was very suprised when i first saw the defferences between .net programming and progress.... but i suppose i've found the problem. The code itself uses a couple of widget-pools for dynamic button...

Hi there, just got a few problems with the transaction rollback functionality of openege 10.1A. 1. discovered problem complete transactions disappeard or have not been performed to the database - there hasn't been any applycation crash at this time. --> for that i tried the -nosavepoint...