>The process of creating the cursor looks ok. Do you know exactly which table trips the "file access denied?"

Currently selected table is always the Cust_curs, although again the two sub-tables are in use and being used by the report.
But honestly, it seems to be more the Report that is causing the problem. I'm leaning more towards this side due to the fact
that I will not receive any portion of the report. Whereas, when I have an invalid field name (or similiar such error on my part)
I'll receive only a part of the report (usually just the header).

>"Once completed, I then have another routine which updates the affected tables. Using these created tables, I then process my report form."
>
>What happens in the routines which those two sentences describe? Do any of them SELECT into a table?

The update routine will attempt to lock the table (loops until successful).
Once locked:
It deletes original record. (yes it does generate quite a bit of deleted records, but great for restoring a previous record).
It will then append blank
Then replace fields with the data from the cursors.
Then I close the table.

The cust_curs is then selected and the report run.


>If it's the report, the advice to copy it to your temp folder is a good idea.

I've been thinking about doing this also (plus those static tables that are referenced quite a bit).

I do have another question: Is it possible to lock a non-database file, and detect that lock with Foxpro?

Thanks.