Search results

As a summary, I tried a lot of combinations with transaction scoping and nothing has changed at all. I will try to figure out if this is a DB file corruption, but if there is no corruption, I have no idea of what to do with this. Recently I had same problem with another script which is very...

Oh, sorry, initially I did not find it in the message editor, but when I specified the CODE tag manually, it looks much better :) I do realize, but this is not a kind of a decision I am into :)

I just tried to remove the TRANSLOOP block and added the transaction word to for each CustomerBills and when I need to undo a transaction, I undo this new one. Nothing has changed at all and the behavior is exactly the same no matter what are transaction scopes. LOL :)

Although changes within for each CustomerServiceChanges no-lock and out of it need to be done within a transaction, I tried but everything remains the same.

Hi. I work with the Progress 7.3D on HP-UX B.10.20 A 9000/785 and, therefore, cannot use anything like _Lock, _UserLock, etc. A couple of weeks ago I had the test environment DB replaced by that from the production. Since there, not much changes were made to the test base. But several days ago...

I'm not the one who decides on a version, unfortunately. I'm working with what the company still has :)

I am already proceeding this way. If it's impossible to shorten the locks timeout, what I'm doing is the only available approach.

The -lkwtmo client command line parameter seems to have been introduced in Progress 8. Is there a way of using anything like that in Progress 7 (on HP-UX)? Maybe another approach? I need to make such a timeout much shorter. Thanks a lot!