>Hi Tracy,
>
>>Which vfp directory? the home() directory or the default directory when the app is loaded.
>
>The home directory. Windows resolves a lot of paths relative to the location of the process image (EXE). That's VFP in this case. Executing an EXE with DO isn't loading the EXE as an executable, rather as an APP. For Windows it would be the same as Word opening a DOCX file.
>
>It still seems that some of the references are resolved differently. This should be visible in the Procmon output. Have you had a chance to run your application with Procmon on a working machine and a non-working machine?

Yes and the entries appear identical. The path to the dll is the same for both and they both appear to be successful on every attempt to read the registry entries for all objects, events and even including COM3. I have traced through both and I don't see any differences (that was a very long process to do). I had entries on the one running inside the vfp ide for the executable as well (whatever.exe) not just vfp9.exe.

However, this morning I received a new api dll with a strong name. I haven't tested it yet, but if it does have a strong name, that should resolve the issues entirely because then it can be placed in the GAC. Or I'm hoping that will resolve all of these issues!