From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
08-29-2014 04:13 AM
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.
08-29-2014 04:30 AM - edited 08-29-2014 04:32 AM
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.
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
08-29-2014 05:30 AM
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.
08-29-2014 05:32 AM
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.
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
08-29-2014 06:44 AM
When LabVIEW does the lookup, it reports both solutions already. So I'm not understanding what your issue is.
08-29-2014 06:46 AM
OK, I did not know that. Thank you.