>>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.

Hi Donald,

Obviously, I don't think there was a CLEAR DLLS issued, otherwise you wouldn't see the reference with the DISPLAY STATUS. However, it could be that VFP's internal memory management may have (somehow) messed the reference up. About all I can suggest is that the functions be DECLAREd only as needed. From what I understand, there isn't a great deal of additional overhead that'll be incurred from the duplication when it happens. This will also guard against another method CLEARing the DLLS.

FWIW, my own general design when working with DLLs is to DECLARE as needed when the object persists throughout the app's session. If the object is only to be used in a particular method that's not subject to any external clearing (short-lived), then I'll declare the functions in the Init method.

hth,