Hi Erik.

>One of my applications has begun throwing 1709 (Database object is in use by someone else) often enough to make my users want to kill me.

I haven't run into this personally, but Bruce Allen of Dallas has and told me about it. The problem appears to be caused by a lock of the view record in the DBC while the view is being opened. If 2 users try to open the view at exactly the same time, this error can occur.

Here are some suggestions until MS fixes this bug:

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

- 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.

- 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.

Doug