Database toolkit installation problem

Being a total newbie with LabVIEW 7.1, I find myself dealing with a lot of problems/questions.
I want to connect to a database. I have tried downloading some sample code like this
http://forums.ni.com/ni/board/message?board.id=170&message.id=26786&query.id=13831#M26786
but when I open this vi(and others downloaded), a window opens asking for the location of "DB Tools Open Connection.vi", "DB Tools Open Connec(String).vi" and others.
Im thinking, maybe I have not installed all the libraries I need for database connectivity?
I have installed the CVI SQL Toolkit.
Can you help or guide me to examples that can?

LabWindows CVI is a different software product of NI to program in C.
LabVIEW can't use the LabWindows CVI SQL Toolkit at all.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Similar Messages

Database toolkit & Oracle 11g, problem with timestamps

I tested my application, based on the Database toolkit, with Access and Oracle XE (10g) databases and all was ok. After moving my database to a Oracle 11g server, i get this error for any query involving a TIMESTAMP WITH TIME ZONE or TIMESTAMP WITH LOCAL TIME ZONE column:
ADO Error: 0x80040E21
Exception occured in Microsoft OLE DB Provider for ODBC Drivers: ODBC driver does not support the requested properties.
The error is raised by the "Execute" invoke node in "DB Tools execute query.vi".
Using Labview 2009 and up to date Oracle ODBC drivers on Windows XP

Hi SnamProgetti,
I don't have any useful information about this error. You can try to read this and this document.
Have a nice day,
Simone S.
Academic Field Engineer - Med Region

Using SQLplus command in LabView Database toolkit

Hi ,
I would like to ask something but before that this is my set up background
OS : Win 7,
LabVIEW : 2012
I have successfully connected with Oracle database using Labview Database toolkit.
The problem now is since I need to query the data from the database,
it will takes time for the labview to process it (since there is so much data in a specific table),
let say that the table in database is "Serial Number", and the data that I want from that table is "SN123"
if I query the data from that table, the labview will process it in a long time since it will not only give me "SN123" but also other data inside the "Serial Number" table.
(Refer to attachment)
but if in SQLplus, there is a command that can be execute to specifically call the "SN123" data,
For the SQLplus, the steps to retrieve the data is like this:
1. Key in the command to get the ID of the "SN123"
2. Key in the command "SN123" ID to retrieve the data.
I wonder if there is a way to put this command on labview database so it will be faster to retrieve the data.
Attachments:
Database.png ‏84 KB

An instrument driver written in Labview, is not the same as a instrument driver used by say Windows. A Labview instrument driver uses standard Labview functions to send SCPI commands to the instrument. You can learn a lot about the instrument by looking into the Labview instrument driver, and how it sends the commands to the instrument. But having the instrument programming manual at hands is also important.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Selecting data on basis of string from ms access using database toolkit

i want to read data from ms access in labview using database toolkit,but the problem is that i want to enter/select pipetype and other fields must be filled from the database with respect to pipe type intead of indexing(1,2,3,....)..kindly tell me how to make my selectio from database depending on pipe type.
Attachments:
database.zip ‏324 KB

What is pipetype and what exactly do you mean by 'selecting data on basis of string'.

Database Toolkit compile problem

We are using the
Database toolkit with Labview 8.2.
If a vi that calls a Database vi is used on
several computers then Labview will ask to save it with the following changes :
VI recompiled and sub vi calls modified.
This happens even if nothing was
changed.
This does not happened
on the computer on which the vi was formerly saved but systematically on all
other computers.
The software configuration
is exactly the same on all computers. The entire Labview directory has been
mass compiled on each of them.
This is very annoying
as we have a lot of database vi’s in our program and all the changes applying
to them hide the real changes to other vi's.
Moreover we are working with an SCM tool
(perforce) which oblige us to have exactly the same vi’s on each machine.
Thank you for your
help.
Nicolas

Hello,
For those following this issue, this was reported to R&D
(#41EBTL3Q) for further investigation. As
it turns out, the problem is that the database toolkit is using strict type
definitions. This would normally not be
significant, except that there is a small problem with LabVIEW recompiling the
typedef when it has already been mass compiled (as is required for the database
toolkit in LabVIEW 8.2).
There is another workaround:
1) Install LabVIEW and the
database toolkit on all your development machines
2) Mass compile the database
toolkit (vi.lib/addons/database) on all the machines
3) Copy the vi.lib database
folder of one of these computers (usually found at: C:\Program Files\National
Instruments\LabVIEW 8.2\vi.lib\addons\database) to a CD (or media of your
choosing)
4) Replace this folder on all of
the other computers with the folder from the CD
5) Use the toolkit as normal
If this doesn't work, you can
also probably check in the toolkit folder to perforce, and just have the users
check it in/out each time, but this situation is a little less than ideal, and
we have not tested it.
This problem will NOT affect the execution of the toolkit
(or LV in
general). Most users will only be inconvenienced
by this problem when using Source Code Control.
Have a great weekend!
Travis M
LabVIEW R&D
National Instruments

Application doesn't work after build (database toolkit and report gen toolkit).

I wrote an application using database toolkit and report gen toolkit to retrieve some data from a database, put into a Word doc, save the Word doc and print it. It works fine when I run the vi, but when I build and run it, it does nothing. I have tried all of the settings in Projec Manager that I think might help but it still won't work right. Labview 8.2.1, XP.
Thanks,
Charlie
Solved!
Go to Solution.

Thanks for the help. I finally abondened the Word append table and used the regular report gen append table and got it to work fine. The error was 214682314. That led me to the thread about column numbers must vbe between 1 and 63, but like I said, my coulumn number is 7 so don't know what is going on. Anyway I got the vi to work and do what I want so I guess now the problem is solved (moot).
Charlie

SQL Query Works in MS SQL Server 2008 but not when using Database Toolkit

I have this SQL query:
DECLARE @DataTypeTable TABLE (
Name varchar(128),
TypeID INT)
--Add comma delimeted data type names to temp table
INSERT INTO @DataTypeTable (Name)
SELECT * FROM WhatWeShouldDoRead.func_Split(@DataTypeTrimmed,',')
SELECT Name FROM @DataTypeTable
Which takes a comma delimited string and returns the string as a table. It works correctly in Microsoft SQL Server Management Studio. When I run this as a stored procedure I get back nothing. There are no errors, SQL or otherwise. I've verified that I am connected to the correct database and that the stored procedure is loaded by changing the no error string that is reported from this stored procedure (that code is not shown in the above example). Has anyone seen this problem before, or have any experiance with SQL/Labview interfaces to tell me what I'm doing wrong?
Thanks in advance.
Solved!
Go to Solution.

After doing some more research it appears that the database toolkit cannot interface with any table results from any type of temp table. It may have to do with the fact that MS SQL 2008 stores temp tables in a seperate database (tempdb) and not the database you are currently connected to. See this link for a good artical on temp tables:
http://databases.aspfaq.com/database/should-i-use-a-temp-table-or-a-table-variable.html
If possible, I'd like a someone to prove me wrong, but for now will have to settle for exporting the contents of a temp table through a string.

Possible DateTime bug in Database Toolkit

Hi!
I dont have the database toolkit here, and it seems you cannot download a 64-bit evaluation ...
Bug? I've been writing DateTime fields to a database through the proper use of clusters and Inserts, but it seems i never get any fractional seconds. The datetime controls shows them and the database fields should support them (atleast it's showing .000 at the end) so i'm wondering: Does it somehow use regional settings for time so it's using my decimal comma and thus ditching the fractions?
/Yamaeda
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV
Solved!
Go to Solution.

Actually if you do a parametrized insert there is not necessarily any string involved. The datatime value could be directly passed as a DB variant. But I'm not sure what the internal LabVIEW conversion from it's native control datatypes to a variant does.
Another idea might be a mismatch with the used decimal character. Some local settings use decimal comma, others use decimal point. ADO, which is used by the Database Toolkit, has a strong preference to use the local decimal format, and so does LabVIEW, unless you disable that with an INI file setting. But if your server uses a different setting you have a problem!
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Reentrant Execution gets slower.... (DATABASE TOOLKIT)

Hi All
I am LabVIEW 2009. Application is typically running on Windows XP.
I have a sub VI which is inserting data in MS SQL server. This vi is using database toolkit for inserting data into database.
I made this VI reentrant, and my toplevel is dynamically calling its clone.
Now suppose if my top level vi opens 20 clones of sub vi, everything seems to be ok. As per logic all 20 clones are inserting data into database parallely/second. (20 records/second)
Now, if my top level vi opens 100 or 1000 clones of sub vi, sub vi's are not inserting 100 or 1000 records/second into database. It means their executions speed decreased. (approx. 35 records/second).
Are my database VI's are creating this overhead or jitter. My SUB vi is reentrant, but when I diagnosed database toolkit, I found that almost all VI's are not reentrant.
After that, I edited all DATABASE toolkits VI's, I made all VI's reentrant, but still problem is unsolved.

Matthew Williams wrote:
As I understand it, the DB Toolkit .vis work through ActiveX, which itself is not re-entrant and may be a bottleneck.
We are battling the same problem, haven't found a good solution. It looks like we will have to go with two queues, one high
priority, one lower that only accesses the DB on a best effort basis. Not ideal.
From conversations with NI, I believe the LV 2010 DSC add-on is multi-threaded regarding DB access. Don't know whether
the improvements are available through the DB Toolkit, though, and we are stuck on 8.5.1 for this particular project.
Matt
Mike Porter has figured out how to get at DB using ADO and aviods the toolkits completely. He is way beyond me in this area but maybe that is an avenue that could help you.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Database toolkit

Hello!
I want to import to Labview two colums of a MySql database.
One of this columns is a column of double. I use database variant data to data, and I specify that is double with a constant....but it appears an error message that cannot convert the input data in this data type.
Someone knows the better way to read in Labview the information of a database....if is a colum of double.....and if is a column of data/time.
P.Derhaps this block only allows you import one element??In this case how i can import it? An Vi's example would help me a lot.
Thanks!!

Hi Bob,
What specific errors are you getting? Does the problem come when the program is run or right when you open it after saving for the previous version? If you already have the Database Connectivity Toolkit 2009 installed (it sounds like you do) we should check to make sure it is activated. To do this use NI License Manager (Programs>>National Instruments>>NI License Manager). If you have not activated products with NI License Manager in the past, it is discussed here.
If you do have the Database Connectivity Toolkit 2009 installed and activated, try to repair the install. Follow the steps in the How can I Repair my LabVIEW Installation? Knowledge Base, but repair the install of the Database Toolkit not LabVIEW.
The next option would be to completely uninstall and reinstall the toolkit. If installing from the disc doesn't seem to be working, try the online Database Connectivity Toolkit download
I hope that info is helpful!
Matt
Product Owner - NI Community
National Instruments

SQL toolkit Win7 connection problem

I'm using CVI 2013 and the SQL toolkit (2.2) tto connect to a mySQL database. I can connect fine using my development computer, but not with the target one. Both computers are running 64-bit Windows 7 Professional (SP1). I was initially using the 64-bit ODBC drivers (mysql-connector-odbc-5.3.2-win64.msi) on both machines. After I had trouble I found a Knowledge Base article that indicated I should probably be using the 32-bit one instead. So I removed the drivers from the target and installed the 32-bit ones using odbcad32.exe found in Windows/SysWOW64. No change.
I'm using the browser2.prj sample project included with the SQL toolkit (by default at: C:\Users\Public\Documents\National Instruments\CVI\samples\sql\apps) to test the functionality of the SQL toolkit. I build a distribution kit including the Shared Run-Time Engine on the development machine and install that on the target. I have traced the problem to the call for DBSources() - it returns a -100 (which, handily, is not amoung the list of database error codes).
On both machines the ODBC drivers appear to be working. I can get to the database using Control Panel->Administrative Tools->Data Sources (ODBC). Selecting the database under either User DSN or System DSN and then clicking Configure will open the MySQL Connector/ODBC Data Source Connection window. Clicking Test in that window will connect to the database.
So the problem seems to lie in the way that CVI connects to the database. I'm clueless at this time, so any suggestions would be greatly appreciated.
Solved!
Go to Solution.

Sorry if this is a stupid question:
Have you followed the instructions in Help->Library Reference->SQL Toolkit Library->SQL Language Reference->Distributing an SQL Toolkit Executable or DLL ?
Or is this an error you are getting despite following those instructions?

Database toolkit install

Database toolkit install problem – multi versions
I have 2 versions of LV installed on a W7 box. The Database Connectivity Toolkit runs fine for the 2009 version. The 8.6 version has broken VIs. Error message - expired or invalid licence.
The tool was not installed properly but every time I try to install it the installer tries to overwrite the 2009 version instead of the 8.6 version. When I do a custom install and try and set the correct location, the installer overwrites the location I set and adds a LV2009 directory.
How can I install it to the correct version of LV?

DKA wrote:
How can I install it to the correct version of LV?
By taking the same version of the Toolkit as the version of LabVIEW is where you want to install it.
Christian

How can I delete a row in access using the database toolkit?

I want to delete just one row of a access table using the database toolkit. Can it be done and if so How?

Take a look at page A-1 of the database connetivity manual. It has information on making a sql query that will delete. You will need to use this command with the dbtools execute query function. Look in the shipping examples for an example with this function.

How to create a database in SQL Server Express 2014 to be used with LV Database Toolkit

I use LV Database Toolkit, which by default uses Jet database. Now I want to use SQL database with LV Database Toolkit. I have downloaded and installed "SQL Server 2014 Express with Tools" in my Labview Laptop. Now I want to create a database in SQL Server, because I think it is a requirement for creating a "udl connection file" (*.udl file). Please help me!
Solved!
Go to Solution.

I made a database whose path is: C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\DATA\depot1
I tried to make .udl connection file, but when I click on "test connection" with the provider: "OLEDB Provider for Microsoft SQL Server" I get the Error "UDL Connection File Failure" (attached below)
When I tried to make the .udl connection file with the provider "Microsoft SQL native Client 11.0" and when I click on "Test Connection" I get the Error" UDL Native Client_1"& " UDL Native Client_2".
Please help!
Thanks!
Attachments:
UDL Connection File Failure.png ‏78 KB
UDL with Native Client_1.png ‏702 KB
UDL with Native Client_2.png ‏714 KB

How to connect labviewv database toolkit to SQL CE server

Dear sir,
i am using labview 8.2.1 and Database Connectivity 8.2.i need same simple concept of how to connect LV database toolkit to SQL CE Server.

When opening the database connection, you will need to provide either a connection string, or a path to a UDL (which will contain a conenction string). The easiest way to get a connection string is to go to (no I am not kidding) www.ConnectionStrings.com. Once there you enter the type of DBMS you are trying to connect to, and the system will list connection strings that you can use based on the drivers that you're using.
How much experience do you have with LV and/or databases?
Mike...
PS: you might also want to check out a series I did a bit ago on database connectivity in my blog. See the link in my signature...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Database toolkit installati​on problem

Similar Messages

Maybe you are looking for

Database toolkit installation problem