This seems to happen when someone is trying to access a table that is opened in exclusive... i was expecting to receive a 1705 error message but i get 1099 instead.
its an old program and it use free tables. Im trying to adapt it to trap 1705 errors (someone is locking table) to allow them to wait and retry instead.
Ok i found the problem... it was my error handling trying to resume something inside a try/catch... the try/catch was cancelling the procedure so i could not return on the line to try again the USE command.
still strange that this error is not documented in vfp.
I had this error recently - I was trying to refer to a top level form from a top level menu I used _vfp.activeform..... and it threw the error - in the end I used _screen.activeform... (vfp9 sp2) which I thought was deprecated now .. ho hum
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.