>- If you're not already, how about opening the views NODATA so the time to open it (and thus lock the record) is minimized.

All of my views are opened NODATA.


>- Your users won't like this (although they'll like it better than "Mismatched Pushjmp/ Popjmp" <g>), but when this error occurs, you could tell them to try again and then release the form and RETURN TO , where is the name of the routine containing your READ EVENTS.

I have implemented something similar to this- the method that calls Opentables watches for a condition and returns .F. if this error is thrown- the .F. trickles back up to the form.load, and I give a message and retirn from there, so the form never instanciates. The user just has to try it again.


>- You could improve the second idea by instantiating a timer before releasing the form. When the timer fires, it re-runs the form, then disables itself. This way, the user doesn't have to manually re-run the form.


Now this is an idea I might play around with if I can't get this worked out right. What I don't understand is why this app gets this error and my others don't (and people like you don't the error... what's different here?).

Thanks for your insight.

Erik Moore
Clientelligence