Seaching in a database

[bleuer]

Hi there

I'm working on a project where I have to find a solution to store quality control reports. I thought about doing it with Labview, storing the information in a DB. Is it possible so select data between a specific time span, or from a specific user, like you can do it in Excel? I never worked with a DB, I have really no idea what's possible in LabView...

Cheers

Markus

Labview 7.1

[becktho]

Hi Markus

Obviously you're mixing up two things. A DB is not LV and LV is not a database. You can use LV to access a database using the Database Connectivity Toolset or other technologies.

Using a database you can select data by different criteria. But this is database technology and SQL - using this you can do almost everything.

Thomas

[Jaime Rodriguez]

With LabVIEW you can write to databases including MS Access, SQL, etc. However, LabVIEW is not a database where you can perform the type of queries you want to do. What you need to do is grab the information you acquire with LabVIEW and write it to a database which you need to create using one of the database managers available. One very nice tool you can use is the LabVIEW Database Connectivity Toolkit. This tool makes it very easy to transfer data to one of these databases.

Hope this helps..

[bleuer]

hey

thanks for your answers...I knew that I need a special kit to access the DB...I didn't write it exactly, I'm sorry.

It looks like reading certain informations out of the DB is not a big problem...I have another question you may be able to help:

I also need something to store reports, generated by the Report Generation Toolkit. This may be word- or excel files with serveral input masks. If I want to look for a specific user, how can I find all the reports he wrote. Do I have to use something like an index-tool which generates a list of my word files with the content, name, etc in separate columns? or is there an easier way with LV?

Also, these word-files should be accessable from different users...with only using 1 DB or whatever to store them in...

thanks

markus

Message Edited by bleuer on 11-03-2005 06:33 AM

[falkpl]

Although many have argued that the DB toolkit is not needed (most who make this argument have extensive background in database SQL and ado)I find it to be a great tool for communicating with databases.  With the toolkit I was able to add a database, insert remove entries and perform queries with SQL with a minimal learning curve.  I had my first database working within one day.  I am finding more and more uses for database interaction and labview every day.

Paul