We have a client that's been running our application for a while, and "all of a sudden" their XP workstations are consistently getting errors like the following:

File c:\docume~1\admini~1\locals~1\temp\00003uvt006y.tmp is read-only.

The error is happening on a line that is indexing the currently selected cursor. The cursor itself was created via a SELECT ... INTO CURSOR READWRITE, yet somehow its status is being changed to read-only.

We downloaded the client's data and tried to duplicate their environment as best as possible (same OS, data residing on server), but we cannot reproduce this error at all. For what it's worth, their server is running Windows 7, and running the application there does not produce the error.

Does anyone have ideas as to why and how this could happen?