I have a DLL written by another party which I cannot change. It is called by a C++ application and is therfore designed with this in mind. I now need to call the same function using VB6.
If I declare the 'raw' DLL and call it directly it causes the VB IDE to drop faster than if using the cross! I therefore wrote a wrapper DLL using the 'standard call' convention in VC++6.
If I now try to declare the wrapper DLL it gives error 49 - bad DLL calling convention - and then the IDE falls over (but much more slowly!).
Has anyone any ideas about this?