Search results

It looks like I'm talking to myself here... I just spoke to a guy from Progress. Apparently, this is not a bug! It is a normal behavior: the internal procedure doesn't have access to the default-buffer-handle of the static temp-table. At least, this is what the guy said. To me this is...

A second thought on your code: ON ENTRY ... DO: RUN Proc_... END. By removing the DO: END. statements, your r-code will become smaller, maybe insignificant, but if you have many triggers, it might help.

If you have a lot of objects and the associated UI triggers, you might want to move some part of your UI into suppress windows run persistently. Depending on the program's structure, this might require quite a lot of changes. Regards.

Hi there, If you have VST (Virtual System tables) enabled, you can find out the user who locked your record by searching in the _Lock or _UserLock tables. I don't know exactly in which one. Check out the Progress Database Administration Guide and reference, chapter 19, page 19-27. If you...

If have an external procedure with a temp-table, and, inside an internal procedure, I create a buffer for this temp-table using the create buffer statement. It crashes with the error: Could not create buffer object for table TT. (7334) However, the same piece of code runs perfectly in the...

Hi Ray, The record is locked as long the block containing your code is executed, supposing you're not inside another transaction. The do transaction solution didn't work because the buffer was used outside the transaction scope, which made Progress to downgrade the lock to share-lock. This...