>I read you thread entitled "VFP5 to 6 Upgrade for jpg". I am working on a project where the API code you supplied will do exactly what I need to do. I was hoping you could help me. I am recieving the following Error: "Cannot load 32-bit DLL ImgDLL" My clients are using WIN95. I am testing on WIN98. Could this be the problem?
>

This indicates one of several problems. The most likely cause is that the DLL is not in the current directory, and cannot be found along the Windows search path (not the VFP search path established with the VFP SET PATH statement.) As a temporary measure, you might try placing the .DLL in the Windows or Windows System directory to see if the problem goes away.

Another, more difficult, problem is that loading the DLL may demand that services provided by other .DLLs or .VxDs, or in rare instances, COM objects, be available and findable. The MS-supplied DEPENDS.EXE, a dependency walker that can determine what the DLL references that are resolved by external calls, could be used to track down other files that may need to be present or registered on the target system. DEPENDS is one of the common tools that comes in the complete Visual Studio system, as well as in the various Windows Resource Kits.

Another possibility (not really applicable here, since it would break under both Win9x versions) is that the .DLL is a 16 bit rather than a 32 bit .DLL, in which case, you need a wrapper to access its interface from VFP. Fortunately, VFP's FOXTOOLS offers this through the RegFn and CallFn services; see George Tasker's Extended FoxTools Help File downloadable from UT for details.