Database connectivity in labview?

when I select the OLE DB provider is "microsoft OLE DB provider for
ODBC Drivers",I can write to database,but I can't read from database
using data connectivity toolkit?
i use the SQL language
SELECT * FROM motor WHERE serial="aaa"
the error is :
"error-2147217904 occurred at conn Execute.vi-fetch record.vi(myvi).
possible reasons:
Invlid string:specified field does not exist or contains an
unsupported character"
but when I select the OLE DB provider is "microsoft JET 4.0 OLE DB
provider" in UDL file,i can read the record using the same language.

Archimedes wrote in message news:<[email protected]>...
> Is it possible the table you are doing a "Select" on contains Chinese
> characters? It's possible the driver you have selected does not
> support Chinese characters.
>
> One suggestion would be to open the database (or table) in Microsoft
> Access and do a quick visual inspection of it. You can check for the
> spelling of the "Serial" column and see if it contains any Chinese
> characters.
thank you for your suggestion.
I have checked the tabel,it contain no chinese characters,my tabel is
below:
serial DT efficiency pf stray
abc 2003-7-2 17:25:09 .02168 1202.556 12.5
I stored data in microsoft access database (.d
b file) and i use the
same SQL language,but get diffrent result,"microsoft JET 4.0 OLE DB
provider"can work,but "microsoft OLE DB provider for ODBC Drivers"
can't read,I don't why?
appreciation for any suggestion

Similar Messages

Run Labview as different windows user (for database connectivity)

I have to connect to a corporate remote MSSQL-Database on the network, using the database connectivity toolkit for LabVIEW.
The db-authentification is realized checking the windows user (ads) who acceses the datebase (not a database user / password which is standard in the database vis)
Therefore I have to run LabVIEW as the defined windows user, different than the logged in user on the pc.
Is that possible to realize with LabVIEW?
Other Windows-tools allow to define the windows user/password which "run" an application - how can I do that with LabVIEW?

Hi Zav. There is a windows command 'runas' which _may_ let you do what you want; I haven't
tried what you need to do, but is has worked for other tasks for us. Try 'runas /?' for the switches.
You will have to build your LV program into an executable, then use runas to launch it. Is there
a reason you can't just login to Windows as the required user?
If you can get your db admin to allow dbuser/password authentication that would be a much better
way to go.
Matt

Please Help me in Labview and MS Access Database Connective

Please Help me in LabVIEW and MS Access Database Connective through an example . I am new to LabVIEW .I need simple example that take a data from a table and display it on front panel .
thanks in advance .

duplicate post

LabVIEW Database Connectivity Toolkit Parameterized Query Property Wildcard

Hi,
within my LabVIEW application I successfully implemented a SQL statement
like
SELECT *
FROM table_name
WHERE property 1 = 123
AND property2 = "abc"
with help of the Database Connectivity Toolkit. I first created a parameterized
query, then set each parameter and afterwards executed this query.
But now I want to use wildcards within this statement. Does anybody know
how to use wildcards with both integer properties and string properties?
Is this possible while using the normal parameterized query vi?
Thanks in advance for your help.
Regards
Michael

Hi Michael
You can use "LIKE":
SELECT * FROM table_name WHERE property 1 LIKE '12%'
% represents multiple characters (e.g. entries with property 1 123 but also 1240 would be selected)
_ represents one character
Hope this helps.
Thomas
Message Edited by becktho on 09-05-2005 11:57 AM
Using LV8.0
Don't be afraid to rate a good answer...

Labview Database Connection Toolkit and decimal point

Hi,
on my system I use "," (comma) as decimal point.
In Labview Options I unflagged "Use localized decimal point", and numeric controls and indicators use "." (dot) as decimal point.
The problem is that Labview Database Connection Toolkit keeps returning floating point numbers as strings with comma as decimal point.
Has anyone experienced this issue?
Is this related to Labview or MySQL ODBC Connector (that I'm using to connect to a mySQL DB)?
Thanks in advance for any help,
Marco

You have two or three places to look. First there is the DCT. Second, there's a couple layers there that could cause problems (the mySQL drivers and ADO) and then there's even the posibility that the issue could be in the DBMS itself.
I would start by burrowing down through all the DCT layers and find the spot where the results are actually being read back fromt he database. If the resutls are read as variants and converted to LV datatypes, the problem is on the LV side. If the values are being read as strings and converted, the problem coiuld be on the other side.
Mike...
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

LabView database connectivity toolkit 1.0.1 compatibility with MS-ACCESS 2010 / Labview report generation toolkit for Office 1.1.3 compatibility with Office 2010

In the very near future we will be forced to upgrade to Office 2010 Company wide and I am a little concerned with some of our older test platforms that have applications built in LabView 8.2.1. These applications save data to MS-ACCESS 2000 databases using the LabView database connectivity toolkit 1.0.1. Office 2003 is also loaded on these test platforms with all test reports generated using the LabView report generation toolkit for Office 1.1.3.
I have not gotten my hands on a copy of Office 2010 yet to see if there will be any compatibility issues. Does anyone have any experience in this area?

The MS-Access part is fairly well isolated through the ADO interface LabVIEW uses. The only possible problems there IMHO are difficulties with possible Acess compatibilities itself such as an example, SQL statement you may have invoked directly through the ADO interface. Maybe you did use a depreciated command back then that has since been removed. As long as the only thing you do are simple INSERT and SELECT statements only, I would expect it to just keep working.
The Report Generation interface is a different beast. Microsoft manages to change the Automation interface with every version of office in a way that strongly binding applications like LabVIEW break on. There is no good way around that except not changing those methods, but that is a cause that has been lost already. You will certainly have to verify the version dependant Report Generation API VIs to still work with Office 2010 and most likely you will have to make some changes to those VIs to make them work again with the modified ActiveX interface of Office 2010. Note, that I have no experience with porting report generation to Office 2010 but I have had some headaches from porting that between Office 97, 2000, 2003, and 2007.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

LabView 5.1 and Database Connectivity Toolkit Compatibility?

I am looking to serve some data from a LabView 5.1 application up to an Oracle 8i database. I have looked at the current Database Connectivity Toolkit (which uses ADO technology), but am not sure if this will be compatible with LabView 5.1... is it? If not, what are my alternatives? Are older versions of this toolkit available?
Thanks!

Also, could someone touch on how forward compatible LabView applications are? In this scenario, I have the same 5.1 application which now requires some database connectivity. Since the SQL Toolkit is no longer supported, I would be left with upgrading LabView to 7.0 and using the Database Connectivity Toolkit. How well (in general) do earlier LabView applications convert to newer versions?
Thanks again!

Why do I get a class conflict between the Prepare SQL.vi and the Get Column Name.vi with the SQL Toolkit compatibility vis from the Database Connectivity Toolkit?

I have done extensive programming with the SQL Toolkit with LabVIEW versions through 6.1. My customer now wants to upgrade to Windows 7, so I am trying to upgrade to LabVIEW 2009 (my latest purchased version) using the Database Connectivity Toolkit, and the SQL Toolkit Compatibility vis. Everything seemed to be going okay with the higher level SQL operations, but I ran into trouble with the Get Column Name.vi.
The pictures below show the problem. The original SQL Toolkit connected the Prepare SQL.vi with the Get Column Name.vi with a cluster of two references, one for connection, and one for sql. The new compatibility vis have a class conflict in the wire because the Prepare SQL.vi contains a cluster with connection, and command references, but the Get Column Name.vi expects a cluster with connection and recordset references.
How do I resolve this conflict?
Thank You.
Dan

I've never worked with the old version of the toolkit, so I don't know how it did things, but looking inside the SQL prep VI, it only generates a command, and the the column name VI wants a recordset. I'm not super familiar with all the internals of ADO, but my understanding is that is standard - you only have the columns after you execute the command and get the recordset back. What you can apparently do here is insert the Execute Prepared SQL VI in the middle and that will return what you need.
I'm not sure why it worked before. Maybe the execute was hidden inside the prep VI or maybe you can get the column names out of the command object before execution. In general, I would recommend considering switching to the newer VIs.
Try to take over the world!

How can I use SQL TOOLKIT concurrently with Database Connectivity ?

I have installed LabVIEW 6.1 with the Database Connectivity Toolkit and the SQL Compatibility Toolkit (e.g. _SQL folder). I am trying to make the transition from the SQL Toolkit VIs to the Database Connectivity toolkits, but for compatability with existing systems I would like to be able to run the two sets of VIs concurrently (but not in the same app).
When I read into 6.1 a connection VI that I wrote with LabVIEW 6.0 and the SQL toolkit the connection reference type gets changed from a number to type connection (see attachments) . Does compatbility mean that my SQL toolkit VIs are converted to a form compatible with the new ADO ?
Can I use the SQL Toolkit VIs or the Database connectivit
y VIs in the same installation of 6.1 ?
Can I have the SQL Toolkit VIs appear on the functions pallette and function as they did when only the SQL toolkit was installed ?
Attachments:
CNNCT.vi ‏20 KB
CNNCT.vi ‏22 KB

In response to your #2 below:
Actually it is possible to have the old SQL Toolkit and new Database
connectivity in the same installation of LabVIEW. I have only tried it on
6i, but don't see why it wouldn't work on 6.1. The trick is not to install
the SQL toolkit compatabitily VI's. The old SQL toolkit uses the Intersolve
dll through ODBC while the new Database connectivity uses ADO so it is
possible to use both methods not only in the same LabVIEW install, but it
the same running application. It has been a while since I originally did
this, so I am posting only to mention that it is possible and not exactly
how to do it. If anyone is interested in more details just respond.
Brian
"Jeff B" wrote in message
news:[email protected]...
> First, direct answers to your direct questions:
>
> 1. Does compatbility mean that my SQL toolkit VIs are converted to a
> form compatible with the new ADO ?
>
> Yes
>
> 2. Can I use the SQL Toolkit VIs or the Database connectivity VIs in
> the same installation of 6.1 ?
>
> No
>
> 3. Can I have the SQL Toolkit VIs appear on the functions pallette
> and function as they did when only the SQL toolkit was installed ?
>
> No
>
>
> Now an elaboration:
>
> Having the old SQL Toolkit and the new Database Connectivity Toolset
> installed on the same version of LabVIEW on the same computer is not
> supported.
>
> Once you install the Database Connectivity Toolset, any VIs written
> with the SQL Toolkit will run, but with the ADO layer, as you
> suspected.
>
> Internally, the only way we can have both the SQL Toolkit and the
> Database Connectivity Toolset installed on the same computer for
> troubleshooting customer issues is to have them installed on different
> versions of LabVIEW. I, for example, have LabVIEW 5.1.2, 6.0.3, and
> 6.1 all installed on my computer, and I have the SQL Toolkit install
> on LabVIEW 5.1.2, and the Database Connectivity Toolset installed on
> LabVIEW 6.0.3. In this configuration I can still run SQL Toolkit VIs
> independent of the Database Connectivity Toolset if I open and run
> them in LabVIEW 5.1.2.

When using the Database Connectivity Toolset, reads and writes with long binary fields are incompatible.

I am trying to write LabVIEW Variants to long binary fields in a .mdb file using the Database Connectivity Toolset. I get errors when trying to convert the field back to a variant after reading it back from the database.
I next tried flattening the variant before writing it and ultimately wound up doing the following experiments:
1) If I use DB Tools Insert Data to write an ordinary string and read it back using a DB Tools Select Data, the string is converted from ASCII to Unicode.
2) If I use DB Tools Create Parameterized Query to do an INSERT INTO or an UPDATE operation, specifying that the data is BINARY, then read it back using a DB Tools Select Data,
the length of the string is prepended to the string itself as a big-endian four-byte integer.
I can't think of any way to do a parameterized read, although the mechanism exists to return data via parameters.
Presuming that this same problem affects Variants when they are written to the database and read back, I could see why I get an error. At least with flattened strings I have the option of discarding the length bytes from the beginning of the string.
Am I missing something here?

David,
You've missed the point. When a data item is flattened to a string, the first four bytes of the string are expected to be the total length of the string in big-endian binary format. What is happening here is that preceding this four-byte length code is another copy of the same four bytes. If an ordinary string, "abcdefg" is used in place of the flattened data item, it will come back as <00><00><00><07>abcdefg. Here I've used to represent a byte in hexadecimal notation. This problem has nothing to do with flattening and unflattening data items. It has only to do with the data channel consisting of writing to and reading from the database.
I am attaching three files that you can use to demonstrate the problem. The VI file c
ontains an explanation of the problem and instructions for installing and operating the demonstration.
Ron Martin
Attachments:
TestLongBinaryFields.vi ‏132 KB
Sample.UDL ‏1 KB
Sample.mdb ‏120 KB

I am using the database connectivity toolkit to retrieve data using a SQL query. The database has 1 million records, I am retrieving 4000 records from the database and the results are taking too long to get, is there any way of speeding it up?

I am using the "fetch all" vi to do this, but it is retrieving one record at a time, (if you examine the block diagram) How can i retrieve all records in a faster more efficient manner?

If this isn't faster than your previous method, then I think you found the wrong example. If you have the Database Connectivity Toolkit installed, then go to the LabVIEW Help menu and select "Find Examples". It defaults to searching for tasks, so open the "Communicating with External Applications" and "Databases" and open the Read All Data. The List Column names just gives the correct header to the resulting table and is a fast operation. That's not what you are supposed to be looking at ... it's the DBTools Select All Data subVI that is the important one. If you open it and look at its diagram, you'll see that it uses a completely different set of ADO methods and properties to retrieve all the data.

How to store jpeg images in SQL server using NI database Connectivity Toolset. Can anyone please help me in this regard.

Please tell how to store jpeg images in SQL Server using NI Database Connectivity Toolset.

http://www.w3schools.com/sql/sql_datatypes.asp
You setup a field as BLOB and store the binary of the picture there. Depending on the database it can be called differently as you can see in the link, in SQL server there's even a Image datatype.
/Y
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

How to read a passward protected excel file with the help of database connectivity tool kit

hi, i was reading an excel file with the help of database connectivity tool kit in labview 8.0
i made tabels in the excel file nand made odbc connection and specified the workbbok name.
now my problem is how to read the same file if i specife a pasword to that excel file ?

Hi,
Check out this thread about opening a password-protected Excel file using ActiveX. This should take care of it for you!
Amanda Howard
Americas Services and Support Recruiting Manager
National Instruments

How to Select Database Path via labview

Hello gurus...........
I am new user in labview. I want read and write in database through labivew . I have
done read and write program. Now I want choose database storage path through labview .
I tried differnt ways but I couldn't.
First read and write program i did via UDL file path .Now i want Directly choose ".mdb" file path.
I dont know how to do ......
So if you know please help me.....
Thanks advance
Regards
Arunkumar M
India

I think the way the database connectivity toolkit works, it is expecting the database to already exist. The function you are calling creates a table so it probably errors if the file doesn't exist. If you google 'create access database programmatically' you may be able to find something useful for creating a new access database file. Don't forget that you also have the native File I/O functions in LabVIEW for copying/moving files on disk.
For the connection string...there's a handy website here: http://www.connectionstrings.com/
I think you can also open a connection file (UDL) in notepad?

Database connectivity

Dear all,
Iam doing my project with database connectivity . the following error is occuring frequently or some time once in 2 or 3 days .
Error -2147467259 occured at DB Tools Open
Connec (String).vi --> DB Tools Open Connec
(Path ).vi -->OQC:vi-->iconsensor.vi.
Possible reasons
Exception occured in DB Provider for ODBC Drivers,
[MySQL][ODBC 3.51 Driver]Cant connect to MySQL
server on 'localhost'(10048).in DB Tools Open Connec (String).vi -->DB Tools Open Connec.
KINDLY POST YOUR VALID SUGESSTION FOR AVOIDING ABOVE ERROR

Hi Marcelo,
Sorry about that, I had a lapse of focus. You are right that this is unlikely to be a Microsoft problem. However, it still looks like it is an issue with the ODBC drivers. Searching google I've found people encountering the same error in Python:
http://groups.google.com/group/mailing.database.myodbc/browse_thread/thread/635e32bd80aefb88/e4b7659...)
and more
http://groups.google.com/group/mailing.database.myodbc/browse_thread/thread/406ef72aab160032/5e9ed45....
The easiest thing may be to check for this error and try to handle it in LabVIEW (perhaps just clear it and redo the database operation).
Megan B.
National Instruments

Database connectivity in labview?

Similar Messages

Maybe you are looking for