调试一个坏DLL调用约定错误 [英] Debug a bad DLL calling convention error

问题描述

我如何调试不好的DLL中MSACCESS VBA code调用约定错误？

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 find the cause?

该错误的函数的exit函数语句出现。

The error occurs on the Exit function statement of the function.

推荐答案

我在Excel中之前，没有任何外部引用看到了这一点。这事发生，因为您的问题，在一个退出函数调用。 Excel中似乎没有有一个/反编译选项，但我固定它通过在我的类模块之一的变化，从调试菜单中执行编译，然后撤消更改。我怀疑我的类模块之一有误编译出于某种原因，和Excel不会重新编译，除非它认为事情已经改变。

I've seen this in Excel before without any external references. It happened, as with your problem, on an Exit Function call. Excel doesn't seem to have a /decompile option, but I fixed it by making a change in one of my class modules, executing a compilation from the Debug menu, and then undoing the change. I suspect that one of my class modules had mis-compiled for some reason, and Excel won't re-compile unless it thinks something has changed.

这篇关于调试一个坏DLL调用约定错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！