> > All,
> >
> > One of our customers is running a VFP COM application with 12 instances on a quad-dual-core server.
> >
> > We're starting to see errors like this:
> >
> >

LINE:1677 ERROR NO:1718 MESSAGE:File
> > c:\docume~1\clinsu~1\locals~1\temp\0000duzd003g.tmp is read-only.

> >
> > Line 1677 is a SQL Select statement against an existing VFP cursor into another cursor. We're assuming that 0000duz003g.tmp is the tmp filename allocated internally by VFP for the result. Certainly it's not something we're creating ourselves.
> >
>
> You could try adding the READWRITE clause to your queries if you want to modify them.
> All query cursor are readonly by default.
> Some simple query cursors are really just the base table opened again with a filter set. You can prevent that with the NOFILTER clause.


That's what I had mentioned to Jack, but he (correctly) told me that attempting to write to a read-only cursor brings about an error 111 and not an error 1718.

Apparently he has two instances creating the exact same temp file name because they are executing the same SQL statement in the same clock tick.

--Brad