This content has been marked as final. Show 21 replies
did you have the problems with the 92102, when you eliminate the synchronizes?
The workaround is to move the Synchronize() after the loop.
Well, I converted the forms straight from 4.5 to 10G. What do you mean by 92102?
but I think that the synchronize is placed to show the processing during the loop.
What about your java bean timer instead.
I used it in the past to make refresh query whith large amount of data.
you wrote : ORA-92102 :-)
So you meant by :
--- BEGIN ---
CURSOR FIND_CLIENTS IS
SELECT C.CLT_NUMBER, C.CLT_NAME CLT_NAME
FROM ALL_CLIENTS C
ORDER BY C.CLT_NAME;
FOR CLT IN FIND_CLIENTS LOOP
:block.item := 'Processing client: ' || CLT.CLT_NAME;
--- END ---
So, would it refresh the :block.item every instance (that's what the business want) or only for the last client? I believe it will only update or refresh it for the last client.
When the 'synchronize' command is removed, the 'ora-92102' did not appear nor did the item get refreshed at all.
Synchronize() is used to "refresh" the client screen (ensure it displays the most recent information). As we run in Web mode, the information about how to draw onto the client screen is get from the Application Server, so that the roundtrip needed.
It is still available in Web version, but needs this additional roundtrip each time it is invocated. So you have to choose between having a screen very close to the truth at any time, but time consumming, or choosing the faster way but displaying the final state only at the end of the process.
ok, try a little test. create a form from scratch and use your functionality in this form with the synchronizes.
I bet it will run without problems. If this is so, then I give you further tips
Can you perhaps direct/guide me to your java bean timer which someone has mentioned earlier in the post? Do you think your java bean timer can be my 'best of both world solution? Thanks.
I've problem straight away running the sample form with the ORA-92102 error. I've used the same code as I've posted at the beginning of this post for the sample form and when it ran, it just failed with ORA-92102 without refreshing my text item for even once.
No, the bean timer would not help at all. Its function is not to refresh anything, but only to act as a Forms internal timer.
can you debug the code, so that you see, when the error occurs?
Excellent example of crossing answer on this topic ;-)))