FRM-92100 error when performing execute_query

Question

Hi,
I know that the connection loss symptom is common, but after reading several posts here in this forum, i didn't find any valuable explain to my problem.
I'm using Forms 6i under Oracle 8i database. My application is used on web environment. I encounter the FRM-92100 in a form that tries to refresh a block after a save.
For that, in the post_forms_commit trigger, i create a timer and when the timer is expired, I only perform a go_block('IQM') and then execute_query. The first time i do that in the same session, all works great, but when I navigate in the 'IQM' records, modify data, and save, here the FRM-92100 raises.
After investigations, the screen fails when trying to do the execute_query. I don't understand why this can be done the first time save but not the second even if the query can be performed in one or 2 seconds ("IQM" is not a huge block).
Is there anyone that already encounters this symptom?. Please help, i'm disappointed

Answer 1

It is just to notice that what i suspected was wrong: Since i modified the 8th record and i have only 5 records displayed in the screens, i thought that the property of the block "IQM" "Number of records buffered" is the responsible of such a bug. I increased this number to 12 to allow the 8th record to be in memory, but no way, FRM-92100 still be raised.
Also, I've tested to remove the GO_BLOCK('IQM') and perform clear_block before performing execute_query. This is to allow the block to position at the begining (since first_record also involves such a bug), and it seems working (no FRM-92100). I will continue working on that to understand why what i am doing fixes the problem. Can anyone have an idea?