I have been working around this bug for a while but finally got fed up with it today and tracked down the culprit. The Database Connectivity toolkit can mask an error if you are doing multiple transactions and you are counting on the VIs themselves to handle an error in the error cluster. In the VI, Conn objectRepository.vi , part of NI_Database_API.lvlib, the VI will mask an incoming error if an error occurs. What you will find is you will get an error 1 from an invalid object which has nothing to do with the error your code generated. This is due to the miswiring of the Error Merge VI which puts preference to the VI's error over the incoming error cluster. I believe the error being generatingby my code is causing the occurence reference to be invalid along the line, because the error 1 always occurs when I try to destroy the connection reference. The fix is to modify the VI to swap the error cluster wiring so the incoming error has preference over the VI's error cluster. See the picture below. Message Edited by Matthew Kelton on 02-11-2009 01:20 PM

Home Community Discussion Forums Most Active Software Boards LabVIEW Topic

LabVIEW

cancel

Turn on suggestions

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

Search instead for

Did you mean:

This widget could not be displayed.