Brad,

If you try to change a value in a readonly cursor, don't you get a 111 error rather than a 1718 error?

The erroring line is a SQL Select that runs repeatedly all day. The filename referenced in the error message is VFP's own internal allocated tmp filename for the result cursor. Presumably VFP isn't trying to create 2 cursors with the same tmp filename, which is why we think it must be 2 instances trying to use the same supposedly unique filename.

The SQL Select does not use readwrite but it does use nofilter.

Our understanding is that VFP always allocates a tmp filename for a cursor but doesn't always spool it to disk. Presumably the error only happens if 2 selects are run in the same clock tick and spooled to disk with the same filename. Again, we're hoping that VFP is smart enough not to try to give 2 cursors the same internal filename which points us back to the multiple instances.