Karl,
I do not know what is causing the problem, but a work-around would be to use a cursor as the data source for the report. You can even close all the 'real' tables before running the report so any problems couldn't harm the tables.

I find that creating a cursor that has ONLY the items needed by the report saves time - both report layout time and running time.

HTH
Barbara

>I have created an application and distributed to my users. I am using VFP 5.0a. In one section I use:
>
>report form sif to print prompt noconsole
>
>In some cases when they print out 50 or more page reports (users with slow printer / PCs with small amounts of memory), they get a run-time error with the message index and file does not match. Delete index and recreate. Then when they restart the software, the primary database IS EMPTY!!!
>
>Users with fast printers have not reported this problem.
>
>Is this a documented problem? is it related to PRINT PROMPT problem. Or is it something I am doing. Is the print job overruning the printer and OVERWRITING the table??
>
>Thanks
>
>Karl Scheff