Is there any way to import a the message table resource from a DLL (or, specifically, an OCX file) into LabView such that the error dialogs will properly report error codes returned by DLL calls?
The only thing you can do with DLLs is call functions, and with the ActiveX interface you can only access the exposed methods and properties. Perhaps you can create a function to return the error string based on the error code?
Yup, that was the fallback plan. I noticed that there's a provision for user-defined codes and messages and would have generated a message .txt file, but the DLL message codes don't fit in the LabView's user code ranges. So fn call it is.
