Hi Walter,

How did you find out, that the problem is report related? Does it happen on the particular workstation or on any computer?

>I have a VFP6 application with a terrible problem that should be easy to fix. It is baffling me.
>
>When a user prints or previews a report from a menu option, everything seems OK. When the user later runs a program, an error message comes up "NOT A TABLE" when trying to open a table that is not involved with the report. This message usually means that a table header is corrupted, but it is not.
>
>If the user closes the application after printing the report, everything runs perfectly when the application is re-opened. Making the report a private data session does not seem to help. RELEASE ALL, CLOSE DATABASES, CLEAR PROGRAM after the report does not seem to help the problem either. The report seems to be leaving something hanging around interfering with common code opening a table.
>
>Any ideas on this mystery??
>Thanks,
>Walter Rothschild