>>Hi,
>>
>>The error (in the title of this thread) is the worst and most dreadful since it is not caused by a bug or bad code but rather the issue with the PC memory (as far as I know). I used to think that the error only happens when the app opens an external DBF file. But lately I see these error (emailed from the app) on attempting to USE/OPEN a DBF included in the .EXE
>>My usual suggestion to a customer coming across this error is to reboot the PC.
>>Any other suggestions on troubleshooting this error?
>>
>>TIA
>
>Best to wrap the USE statement into a method which can handle any unforeseen issues.
>
>Usually you would not want any error occur during USE, so whatever error you get you may want to close the app anyway. Therefore you can just do a try/catch in the useTable() method and if failure, then CANCEL, or even better, kill the process.
>
>Also it could be an idea, if you get an error in the try, to build in a loop where you can sleep and try several times. (I use this for example when running SQLEXEC and if the server is down it keeps retrying until the server is restarted. This way I can restart the database server without worrying for the users, they just have to wait a little and the program continues automatically.)
>
>Also good would be to write a log file on failure with the error number and message you catch, calling procedure, timestamp and pc name

Thank you. Good suggestions!