Debug a bad DLL calling convention

Question

How do I debug a bad DLL calling convention error in MSAccess VBA code?

I made some changes to a function in a module and then got the error. How do a debug it to fi

Answer 1

In Excel VBA, this can be caused by any of several problems:

1. A parameter or return-value type mismatch.
2. An object method (such as AutoFit) applied to an erroneous object variation for which that method isn’t available.
3. A call to an external library function.
4. Broken library references

For resolutions to these causes, see my post at: Runtime Error 49, Bad DLL calling convention