I would check for a change of the data session. Just had a case where that was the reason for a similar problem.

HTH
Gerhard

>Hi Gang!
>
>Just need some suggestions as to where to look.
>
>We have a LARGE application, written VFP 9.0 SP1, that until recently behaved ok. Since the last update, the users are reporting daily errors, which we capture in a table to examine.
>
>The errors are occurring in 1 form, and this form has a PRIVATE DATA session
>
>The errors, that are new errors, are predominantly of the kind where the tables are not being used or open, when normally they were.
>
>I checked in the code for any
>
>USE
>
>by itself and maybe closing a table by accident.
>
>Also looked for things like USE footable without a SELECT 0 before it, or IN 0 in it.
>
>I also added a new method (base on ideas given to me from here, on the UT). The routine was to enable a DUPLEX capable printer to actually print in DUPLEX for reports and monographs printed out during prescriptions as they are being filled. Here is the code for DUPLEXING.... ( the idea here is that the report forms are IN the executable, so I have to copy the structure of the report form to my TEMP folder, there rename it to be a report again, modify one of the fields that holds the DUPLEX information, save it and then use this modified report to print the report information.)
>