>Hi To all,
>
> I made an application in VB and DLL in VFP (say Computer A). When the app in VB and DLL in VFP were transferred into another PC (computer B), i got an error in VB saying "Error loading DLL (error 48)". In order to run correctly the DLL file made in VFP, I tried to get the source file from computer A and have it build again into a DLL file using computer B, then it works properly.
>
> What's happening here? Do I have to build the DLL file exactly where the app should run on a particular machine?
>
> Note:
> 1. Computer A and B runs on WIN95.
> 2. DLL file was registered correctly using REGSVR32.exe
> 3. Both Computer a and B had the VFP libraries.
>
> any explanation will be highly appreciated.

Hi there Victor,

What does the VFP DLL do? Does it use any tables? Do you have the proper pathing in place? In my experience, when a VFP COM object loads from the DLL, the currect, default directory is the WINDOWS\SYSTEM or WINNT\SYSTEM32 folder where the VFP runtimes are located, not the folder where the DLL was registered.

If your DLL is in the same folder as a table that is used, just issuing a USE {table-name} will generate an error. You need to qualify the path for local files.

Phil