Simple local database

[HIlg]

Hy there,
Hopefully an easy question:
All I want to do is creating the simplest possible data base on my own PC,
insert data and retrieve it afterwards. I want to use LabWindows/CVI 5.5
with the SQL Toolkit 2.0.

I think, txt file data bases are the easiest ones, right?
So I created a system DSN as CVI SQL txt file with the ODBC Data Source
manager, created a file and defined its fields in the ODBC Manager.

After that, I connected to this database with DBConnect ("DSN=TEXT_BASE");
which delivers a valid data base handle (1) without an error message.
But as soon, as I try to execute an SQL command "INSERT INTO TT_TABLE1 ..."
the message "Automation Error Code 0x80020003, Member not found"
If I try to read from the data base via DBActiv
ateSQL and DBBindCol... the
DBFetchNext function delivers DB_EOF on the first call although there are
some rows in this text file

1.) What is the easiest database to create locally?
2.) Which "member" is not found when trying to insert a record?
3.) What is wrong?

When I run the sel_info.prj project, a list of all the defined tables is
displayed, but as soon as I select one and the app tries to execute an SQL
statement (SELECT * FROM tt_table1) the error "ODBC driver does not support
the requested properties: appears.

Thanx
Harald

mailto:Hilg@gmx.net

[Chris_W1]

Harald:

Initially I would think that the SQL conversation handle you may be passing to the SQL calls may have a problem. Have you been able to successfully run any of the shipping examples with the SQL Toolkit?

It may be best to continue this discussion with National Instruments Technical Support. You can contact Technical Support via email at http://www.ni.com/ask or by calling the number for your area listed on the page at http://www.ni.com/support/wrldwide.htm .

Good Luck,

Chris W
Applications Engineer
National Instruments

[HIlg]

Hy Chris,
thanks for your answer, meanwhile, I am convinced, that this behaviour is
due to system problems. I tried the same thing on another machine and it
worked fine.
So I guess, there is something wrong with my NT setup...

Thanx
Harald

mailto:HIlg@gmx.net

[HIlg]

Hy there,

Ok, after solving the last problem with simply declaring it as system
problem, here's another one:

After successfully connecting to a database, I would like to execute a
SELECT statement.
No problems with simple ones without WHERE.
But as soon, as there is a condition in it, I get the message "The request
properties can not be supported by this ODBC Driver."

Doesn't it say in the online help "The driver supports all Select statement
clauses as described in SQL for Flat-File Drivers" and the WHERE is in
there?

Thanx
Harald

P.S. Here my SQL Statements:
This works:
SELECT MEAS1, MEAS2, MEAS3, MEAS4 FROM APP_TEMP
This not:
SELECT MEAS1, MEAS2, MEAS3, MEAS4 FROM APP_TEMP WHERE UUT=1303

mailto:HIlg@gmx.net

[HIlg]

Hy there,

> Ok, after solving the last problem with simply declaring it as system
> problem, here's another one:

Found it!
So no problem at the moment, sorry for the inconvenience.

Harald

mailto:HIlg@gmx.net