I've got a program that runs continuously that analyzes some signals. On a rare occasion, the user will see some interesting signals, and I want to give the user a toggle button to turn on/off logging of the signal to a SQL database without stopping the Labview program. Plus, I want Labview to re-connect automatically to the database should the database server need rebooted. The problem is detecting whether a database connection exists every time I run through the datacapture/datalog sequence BEFORE I attempt a database insert. I called tech support, and they said the only way to do this was to attempt a database insert, and if I get an error, then try to create a connection. While that method does work, its not what I'd call a good solution (I like errors to be true exceptions to be handled, not just standard operating methods).
My original attempt is coded in "db connection exists test.vi". This code does NOT properly detect the existence of a database connection and continues to establish a new connection every loop. This is proven by watching current processes in SQL and seeing them blow sky high when I run the vi.
The NI tech solution is coded in "db connection error test.vi". This code does work, but I am trying to get its functionality with better programming methods.
Both examples log to a database server called "devbox", database called "test", username "test", password "test", table "test", containing a single varchar column called "col1".
As I add other database functionality, this "error test" method is gonna become really clunky. Does anybody have any ideas on how to do this properly with the enterprise connectivity toolset or other methods?
Thanks in advance,
Jason
Message Edited by JSat on 10-21-2005 09:39 AM
