调试错误的 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屋！