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

We've run into some problems with VBA when trying to call a DLL compiled in Intel Fortran. It turns out that you need to align the calling conventions back to a "C" context with the compiler flag calling convention: cfv

More info here on the Intel website Another useful thread on the same problem: Intel Fortran DLL <-> C