调试错误的DLL调用约定 [英] Debug a bad DLL calling convention

问题描述

如何在MSAccess VBA代码中调试错误的DLL调用约定错误？

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中已经看到了这一点，而没有任何外部引用。与您的问题一样，它是在Exit Function调用上发生的。 Excel似乎没有/ decompile选项，但是我通过在一个类模块中进行更改，从调试菜单执行编译，然后撤消更改来修复了该问题。我怀疑我的班级模块之一由于某种原因被错误编译，并且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屋！