>>I am troubleshooting an error 52 - No table is open in the current work order. The user(s) who get this error never report it but my error log file shows it. So I need duplicate and fix this.
>>
>>I suspect that the following line of code in the procedure causes this error:
>
>embolded word suggests that your error handler needs some work ;-)
>
>Recreating the exact conditions for spurious errors to occur can be PITA - I remember from a vfp bug encountered in vfp6 where an alias name recently closed was not always freed in time to be reassigned if the code asks for it a few lines later. Bug is gone in vfp9 (at least does not show up in my apps, where it happened regularly a few times in most months) so your case probably is different.
>
>But the method to track and work around the vfp error might help you as well: wrapping all use / close / select in own functions, adding a log in those functions so you are able to recreate the relevant LOC just before error crops up. Do yourself a favor and tag the version before such changes in your source control software ;-)
>
>In my case those temp wrappers (including temporary fixes found by Aleksey and myself) were in action for a couple of years, as the bug WAS a vfp bug.
>
>HTH
>
>thomas
>

Thank you for all your suggestions!