Occasionally after a find, IWP seems stuck on record 0 of the found set (which contains several records). In the status area, the record number is given as zero. FM Pro users don't get this problem, just those accessing via IWP.

This stops any scripted buttons working, and brings up a "Record Not Found: The specified record was not found." dialog box every time the user tries to do something. A workaround is to reveal the status area (which I like to keep hidden from users) and go onto record 1 that way. However, scripted buttons to do this don't work, so I assume the status area buttons in IWP work at a lower level than FM scripts.

I tried to put a button on my IWP screens with a "Go to first record" script step to let users recover from this situation, but even when clicking this, IWP just returns the "Record Not Found: The specified record was not found." dialog, I assume for the reason above. The file is running on FMSA 7.

I have seen the same problem from time to time. I hope someone comes up with a good answer...

I find it happens when users use browser refresh or back buttons. Therefore, I open the database in a window without chrome -- so far no problems.

It sounds to me like the find is not matching any records, evidenced by the fact that you have a empty found set (that's what the zero means, not "record zero").

Review your scripting to trap for and deal with an empty found set. You might want to look into the Set Error Capture [] and Show All Records script steps, and the Get( Last Error ) function.

This doesn't happen as the result of a find. I do trap errors and check found counts. You can be reviewing a record and simply hit "refresh" via the browser and enter this state.

The solution of removing chrome works to avoid the problem.