LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

about nonfatal runtime error in CVI

Solved!
Go to solution

Good day

My program:DBNumberOfRecord() gets a nontatal runtime error when I debug it, if I press continue it gets normal work. So I think the error dialog is improper, but i cannt skip it.

 

Can i skip the error when debugging? thank you!

0 Kudos
Message 1 of 4
(4,734 Views)

Provided you are sure this error is meaningless, you can skip all library errors with Run >> Break On >> Library Errors menu option



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 2 of 4
(4,731 Views)
Solution
Accepted by topic author justtin

During debug of an application under development it may be excessive to filter out all library error messages. In this case you can enclose your faulting instruction between a pair of SetBreakOnLibraryErrors () calls that disable and then re-enable popup error messages.



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
Message 3 of 4
(4,725 Views)

Thank you for your answers!

Using the function SetBreakOnLibraryErrors solved my problem properly. Thanks.

0 Kudos
Message 4 of 4
(4,717 Views)