>Hi Tracy,
>
>as the Dll seems to be a kind of mediator, how about talking to that mediator not from vfp but from other directions ?
>First of all I'd try accessing the mediator from another dotnet app to talk to the 3rd party
>to make sure instatiation does succeed there - should work with and without COM registration.
>If that works, COM barfs - then I'd quick check vfp object browser
>but head rather straight for VB6 for fürther tests. FileMon/Procmon on your USB ?
>Just log in case of security raising one hydra head...
>
>regards
>
>thomas

I can see it in the object browser in vfp on those systems that have the full developer version of VFP. On some it will communicate, and others not. What doesn't make sense is that it communicates fine on some machines with no vfp (only the runtimes) but not on others as well. When I check the registry the entries are there and the location of api dll is included.

What could possibly be different between the machines that work and the ones that don't?