saving labview data to a database

[tst]

Great paper, Mike.

A couple of comments, in case you plan to ever post it again.

At the end of the first paragraph, you wrote "brought up the whole issue of decoupling—and how to prevent it.". I somehow have a feeling that you are not interested in preventing decoupling.

In the bibliography (#4), you wrote schelp instead of schlep. Yiddish just doesn't work if you don't use it right (ever watched "City Hall"?).

One last question, can you post anything regarding the VI server you mentioned in part 3 (code\images\desing papers\anything) or do you consider that proprietary?

The reason I ask was because I wanted to see how you handle decoupling and design in general in LV.

And while I'm here, one question about your Error Fork VI - It's a great idea, but it only takes the higher error number out of the 2 errors - what happens when you like to control the code based on error numbers (like timeout errors)? Do you do the checking before merging? Do you only use it in places where you don't check for error numbers?

[mikeporter]

Hey tst;

Thanks for the edits! Actually I know how to spell schlep--it's the typing I not so good at... Concerning your notes on my VI for combining error streams, the observation you made is sort of an artifact of trrying to do something useful, when complete isn't possible. When combining errors you can certainly build up arbitrarily complex source messages, but you only have one error code field. I have had the idea for some time to create a "compound error" error code that would notify the user to parse the source message for more details, but I haven't had time to do it yet...

Mike...

PS: concerning the application server stuff, contact me back-channel.

mlportersr@earthlink.net

[Gurdas]

All,

We've been using the Database Toolkit for some complex and distributed applications. Multi-user, many tables and as many fields. When I started, I had never worked on any database before. A good look at the examples and help from team members working in VB and SQL got us zipping. We have never looked back since.

If there are specific questions of smart usage, queries, parametrisation and stored procedures, I'd be glad to help.

Crystal,

I have a problem with using NULL values in parametrised query. The post is at:

http://forums.ni.com/ni/board/message?board.id=170&message.id=136682

Can you help?

Thanks,

Gurdas

[Albert.Geven]

Very good question.

Talking to databases via the NI toolkit does not help this very much. Using stored procedures on the database side and dedicated vi's on the labview side can make this work very good.

Just like Instrumentdrivers help you to abstract the instrument to a set of vi's, stored procedures hide the database implementation from the data acces.

Use, or look at the T&M database wizard (look in LabVIEWmasters.com)

succes