The real problem here is that you have different error codes for different modules inside of LabVIEW. I imagine it could still be done.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions Unofficial Forum Rules and Guidelines "Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
There are only two ways to tell somebody thanks: Kudos and Marked Solutions Unofficial Forum Rules and Guidelines "Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Yakov: There is no list because the list is open-ended and shifts depending upon what modules you have installed. If you want to see a list of the error codes, open up the *-errors.txt files that are on your disk. The ones in <labview>\resource\errors are the ones for LV core. The ones in <labview>\user.lib\errors are installed by third-party libraries. The ones in C:\Program Files\National Instruments\Shared\Errors\ are from hardware drivers. Collectively these define the error codes on your particular system.
There is no list of errors from the other modules because when LV ships, we don't know those errors. Each module/toolkit (including from third-parties) can install additional errors. That's why if you want this information, I was pointing you toward the error code text files.
Perhaps the best solution here is a dynamically generated list of codes and descriptions based on what is present on the system. It seems like we could provide a Help menu option that runs a VI and generates a dynamic HTML page with that info.
Yakov, given what AristosQueue said about the dynamic nature of the errors.txt files on the system, would a separate tool to generate information about locally-installed errors be a viable solution?
"Perhaps the best solution here is a dynamically generated list of codes and descriptions based on what is present on the system. It seems like we could provide a Help menu option that runs a VI and generates a dynamic HTML page with that info."
You mean like the error ring (Perhaps searchable)
Whatever is going on behind the scenes in that select error dialog ALLREADY generates a dynamic list from whatever in installed- redirecting its output to a HTML file ought to be relatively painless (For me at least- maybe not for the developer) Unless.... Hmmm If you don't pick that up 8-Ball might, I like that idea
Given the dynamic nature of error messages, the concept of a VI to get them sounds useful. Even better would be a list specific to a VI named (or by refnum) as an input to the Get Error Messages VI.
Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.