I've got a problem with a multi-threaded DLL written in VFP6.0 SP5 where it's acting inconsistently on a Win 2003 server with two Xeon dual-core CPUs (Task Manager shows 4 CPU) -- there are times where certain operations within the DLL work and other times where they don't. The COM+ DLL was registered to work with a specific identity -- a user with limited access (basically the folders in which application resided). After adding some debug information to the code and tracking what's happening, I started noticing a pattern. Whenever it worked OK the SYS(2023) was returning C:\WINDOWS\TEMP (i.e. the system temp folder). In the situations where it would not work was when SYS(2023) was returning blank. I've noticed that the CONFIG.FPW doesn't seem to have an effect on DLLs. According to what information I was able to locate, the value returned by SYS(2023) is based on the TEMP or TMP environment variables. In the debug code I included value returned by GETENV("TEMP") -- and it consistently returned C:\WINDOWS\TEMP (i.e. the return value was always the same, but SYS(2023) would sometimes return C:\WINDOWS\TEMP and sometimes it would return blank).

Can anybody shed some light on what's happening here? Does this have anything to do with host computer having multiple cores? Is there a workaround for this?