saving labview data to a database

[falkpl]

Good to know, I shouldn't hit the 2GB limit any time soon, I will give the database a try.  I think it will help me with tracking my data.

Paul

[roboticstudent]

---

@falkpl wrote:

Thanks for all the help, I will try out all the options.  The databasing is fairly simple, I have 2-3 tables and each table has 5-10 fields, I got it working on access and was able to communicate with it through the jet engine on windows XP PRO from my labview application, I am very pleased.  I will try out mySQL and compare it to access which I already own.  It is good to know that I don't need more than the ADO objects and the JET database engine and a .mdb file to communicate with the database.  Again all the input has been very helpful

-Paul

---

May I see what your code looks like for the table and fields your created using Access and LabVIEW?

Thanks.

[mikeporter]

To echo the roboticsstudent, if you post your SQL code as well as your LV code that you use for talking to the database, I can advise you on those aspects of your project as well.

Mike...

[Arnoud]

Hi,

Since working with databases is not an everyday practice of most LabVIEW programmers and the National Instruments Database Connectivity Toolkits doesn't make life easier we have created a Toolkit that makes LabVIEW and database programming much easier!

With use of the newest technologies available in LabVIEW, such as GOOP, Express VI technology and Automatic LabVIEW code creation, this toolkit enables you to work with database without having to know how they work.

Some important features are listed below:
Use LabVIEW Express VI technology to browse your Database Structure interactively.
Automatic datatype conversion to familiar LabVIEW datatypes (Newest Technology!)
Automatic generation of Structured Query Language (SQL)
Easy maintenance of databasestructure


To see the complete product specification see:
T&M solutions Database Toolkit for LabVIEW

If you are interested or have any other questions please do contact us.

Arnoud de Kuijper
T&M solutions
http://www.tm-solutions.nl/eng

Just see how simple your LV code can be:


Configure the database actions with the use of Express VI's

[mikeporter]

Yes, a great solution--and for "only" $2400 US!!! (2940 euros)

Better you should take a week and learn how to do the job right yourself... At least then you'll know that the mechanics of interacting with the database is the (very) easy part. The idea that you can buy any toolbox and not have to learn about databases is a myth. And in this case a very expensive one.

Mike...

[Arnoud]

Hi,

I understand the fact that you are sceptical about this toolkit, but that is because of the nature of database programming: In General it is difficult, time consuming (if you are inexperienced) and not easy to implement. THAT is exaclty the reason why we have created this toolkit, as you might have seen on the screenshots above all is guided by a click-and-get userinterface. Expecially the automatic code generation in combination with the Express VI's makes it very powerfull.

I understand that it's interresting to learn the mechanics of interacting with the database yourself, but if this takes you 1 or more weeks to learn this might be more expensive than the price of the Toolkit.

With kind regards,

Arnoud de Kuijper

T&M solutions BV

[Philip_Courtois]

---

@Arnoud wrote:

...the National Instruments Database Connectivity Toolkits doesn't make life easier...

---

Hi Arnoud,

Wow, your Toolkit looks great for people that don't want to get their hands dirty in the DB-mud. However, I can't agree with you that NI's Database Connectivity Toolkit doesn't make life easier for people. I have seen countless examples of customers that started without no previous knowledge of DB programming and after a very short time was up and running - only because of the toolkit.

There's a place for everything...

Message Edited by Philip C. on 08-09-2005 04:19 AM

[mikeporter]

That's right, keep spreading the fear of "database programming". They only problem is that it isn't any of the things you said ("difficult", "time consuming", or "not easy to implement"). It took me about a week to originally develop the drivers that I use--and that included learning ADO. Bottom line: talking to a database is very, very easy, and the vendors have excellent tools to assist you. But you still aren't addressing the real issue: How to properly utilize a database.

Unfortunately, you will no doubt sell several copies of your toolkit to people who get taken in by your FUD, but eventually the word will get around about how little value it gives for the money.

Mike...

[falkpl]

A little update on this thread I started.

I have moved all of my data saving from multiple XML files to a single database using the NI tool-kit (I already had it with the professional developers suite) with little trouble.  I have 8 years of labview use, a Masters Degree in CS (and I managed to never take a DB course which has mostly become an it requirement unfortunately) and a few additional years of programming experience, so I am not a novice.  But none the less I found getting started to be easy (a 2 out of 5 degree of difficulty).  The only issue I had is the expandable of the database.  If I want to add additional columns to the database I might have to alter the code because I found adding a record to be difficult.  I used insert data and passed the data as a cluster equivalent to the record set entry.  Is there a better way to do this?  I had trouble passing a record with only a few columns filled out and could not get the variants to work either.  Reading from the database was easier than writing to it, but I will still have to learn morn SQL.  I write about 5 medium scaled LV applications a year, mostly for R&D purposes and most will gain from a database storage solution.  Hopefully I will master it over the next year or two.  Thanks for all the help.

Paul

[Arnoud]

Hi Paul,

I understand you problem about correctly writing to databases, you need to understand that a database server like SQL server has different datatypes that LabVIEW. If you do not wish to build SQL commands with your data as string you have to use the ADO.Command object, this allows you to pass binary data. But before you can send binary data you have to set some datatype properties:

Please Note the following:

1.  The conversion path for datatypes should be:

 a. From LabVIEW to Microsoft ADO.

 b. From ADO to Database Server.

2. Inserting data from LabVIEW to a Database Table will concern converting your LabVIEW data to an Array of Clusters. Each Cluster is the record to insert.

3. It is also possible to alter your database structure, but I do not found this advisable. You should use SQL commands like: ALTER TABLE [xxx] ADD [COLUMN]

If you have any specific questions or problems please do ask, or post you VI!

With kind regards,

Arnoud de Kuijper

T&M Solutions BV

Message Edited by Arnoud on 08-10-2005 03:07 AM