Re : Custom error code conflict

[LarsM]

How should error code conflicts be resolved?

Imagine that I have installed two VI packages that happen to have overlapping error ranges for their custom errors. How are the overlapping errors resolved?

The LabVIEW help says that this is already the case. The example given is error code 65. However, the help does not give any indication how to resolve this. It links to an empty page in the knowledge base.

[TiTou]

This link tells you the range of error code that you can use for custom error codes, if you stick to that, the chance you of overlap will be reduced.

[LarsM]

Yes, I know that. That was not my question. My question was: how are conflicts resolved, once they appear?

The LabVIEW help already mentions at least one existing conflict.

[TiTou]

Sorry... I think that o resolve such conflicts you need to change one of the two ranges, which means you need to have acces to the code of at least one of them to change the error range you are using.

[crossrulz]

When LabVIEW does the lookup, it reports both solutions already.  So I'm not understanding what your issue is.

[LarsM]

OK, I did not know that. Thank you.