> Thanks for your help, but I already ran Depends on our C++ DLL to
> verify dependencies, and there are none missing, so I believe this
[quoted text clipped - 3 lines]
> we also access another DLL, coded in C++.NET, and this one we can
> access on every PC AND every tablet we have.
That points even more strongly toward a missing dependency.
Rather than just running Depends on the DLL, run your program from within Depends, and generate a log. This is the only sure way to verify that everything needed is present and correct.

Signature
Jim Mack
MicroDexterity Inc
www.microdexterity.com
Fueled - 30 Mar 2006 17:47 GMT
Hi Jim,
Thanks for your suggestion, i will try it.
Could you explain how to run my application into Depends?
You see, our main DLL is coded in VB, and from this main DLL we access
the other one coded in C++.
Our main DLL is actually running inside AutoCAD.
Thank you again.
Simon.
Jim Mack - 30 Mar 2006 20:01 GMT
> Hi Jim,
>
[quoted text clipped - 6 lines]
>
> Thank you again.
In newer versions of Depends there is a feature called 'Profiling'. Start Depends by itself, then use the File menu to load your program. The View menu should have an entry titled 'Start Profiling'. This spawns your program so that Depends can watch every LoadLibrary and GetProcAddress call. Certain 'errors' are normal and expected, but true errors should be fairly easy to spot.
Obviously, you must do this on the failing machine for it to have any value.
Good luck.

Signature
Jim Mack
MicroDexterity Inc
www.microdexterity.com