I had to specifically trap for this error when calling the Form.Dataenvironment.openTables method, and if the erro occurs, return .F. from the form.load. The user then has to try to open the form again. This is sometimes a pain in the ass, but so far, is the only solution I can come up with. I have spent probably a total of 3 hours on the phone with MS level 2 support trying to resolve this, and the guy I was talking with threw in the towel and called it a bug. I had sent him a sample program that reproduced the error consistently, and it could not be resolved.

All this would be unnecessary if RETRYing from the error handler did not cause the 'mismatched pushjmp...' error.





>Did you ever resolve the 1709 error? Which approach did you take?
>
>thsnks
>>Ok, this is a last ditch effort before I call Microsoft. 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 have yet to get a clear picture of what causes this error. A search on the MSKB turned up an article that recommends a simple RETRY in the error handler when this pops up. So I put this in the very first line of my ON ERROR routine. Now, instead of popping up an error message, I get "Mismatched Pushjmp/ Popjmp" from VFP (this is not a trappable error), and clicking ok causes the program to quit.
>>
>>I just spoke to a user that said this happened to her 5 times already this morning. This is the only app I've written that has this problem... what is going on?