>>In our VFP 5.0 application (ported from 2.6) we DECLARE several functions in WIN32API.
>>
>>On a rare ocassion, we somehow "lose" the connection to those functions in USER32.DLL, but not KERNEL32.DLL. VFP nicely catches this error, and we don't get a GPF.
>>
>>For example, when things are normal, DISPLAY STATUS will show:
>>
>> GetForegroundWindow c:\win95\system\user32.dll
>>
>>When things are screwed up, DISPLAY STATUS will show:
>>
>> GetForegroundWindow c:\win95\system
>>
>>All of the functions (8, total) we need from USER32 are gone; all of the functions in KERNEL32 (15) plus another 20 in other DLLs are fine.
>>
>>Any ideas?
>
>Hi Donald,
>
>I've never seen anything like this. Can I assume that if the file name of the DLL is not showing, that the function cannot be called?

Yup. There specific error I get is 1753 "Cannot load 32-bit DLL c:\win95\system\." Help on the error is rather terse, and Devnet/Technet yield no more information.

This function was DECLAREd when the CPU was booted; the error occurred the first time it was called (I think), about 5 minutes later.