I'm building multi-threaded .dlls based on a session class. I found this when attempting to make the cursor returned from a SELECT statement read/write with this standard trick:

SELECT * FROM MyFile INTO CURSOR csrTemp1 NOFILTER
USE DBF('csrTemp1') AGAIN IN 0 ALIAS csrTempReadWrite

It tells me the file isn't found. Oddly enough, the path to the file it's showing me is bogus. I then started to use SYS(2023) to retrieve the temp file path and it was returning the same bogus path.

Some facts so far:
all test machines are Win2000 so far SP1 or SP2
VFP is 6.0 SP3 or SP5
aside from this one statement, the corrupted path seems to have no effect
doesn't seem to happen in single-threaded .DLLs
doesn't seem to happen in .EXEs
on SOME machines, goes away if the .DLL is run in COM+

Have tried:
uninstalling/reinstalling VFP
uninstalling/reinstalling Win2000 SP
running SFC for Win2000
virus scanning
VFP SP3 and SP5

I suppose I could skirt the issue by grabbing SYS(2023) on startup, before it becomes corrupted and doing this:

lcTempDBF=This.TempFilePath+JUSTFNAME(DBF('csrTemp1'))
USE (lcTempDBF) AGAIN IN 0 ALIAS csrTempReadWrite

But it worries me that there seems to be internal corruption in the libraries...