Managing custom error codes

[Bublina]

Hello,

I know we have the custom error codes editor, but this sort of data stays only within LabView folder (please correct if I got this wrong)

So if I want to keep track of my error codes around my project, how should I do it.

I manage custom error codes now simply through a VI that I use as a constant for errors (enum in, error out).

[paul_a_cardinale]

I try to avoid custom error codes.  Usually I find a built-in error code that fits, then add in a possible cause.

See the attachment and http://forums.ni.com/t5/LabVIEW/Error-Rings/m-p/2337862

[Bublina]

Thanks for answer, but your solution does not solve my problem completely. Nice VIs though.

I use custom error usually for implemented DLLs that allways bring some new functionality, that is missing in LabView. Further, I use custom errors for standard programming in cases, that should never happen, like timeouts is queues and so on.

So basicly I have an library and this library should have its own custom error codes, that should not overlap within the project it is used in.

[Ardent]

Hi Bublina,

personally I just bundle the error listing file to my installer and/or standalone executable - this help file describes it. Not sure this solves your problem but I guess it might.

As I understand, you have the error handling part figured out, but I would still point you out to the SEH reference library (stands for Structured Error Handling). It has nice architecture as well as local and global error handling capabilities.