Confused about which version of LabVIEW Database Connectivity Toolkit to buy

[cxl6288]

3 versions of LabVIEW Database Connectivity Toolkit can be found on NI website:

-LabVIEW Database Connectivity Toolkit

-LabVIEW Database Connectivity Toolkit 2013

-LabVIEW Database Connectivity Toolkit 2014

According to NI, 2013 version work with labVIEW 2013, 2014 version work with labVIEW 2014. What about version of LabVIEW database Connectivity Toolkit. Does it work with all labVEW version.

I am using LabVIEW 2013. if I buy LabVIEW Database Connectivity Toolkit 2013, do I need to buy LabVIEW Database Connectivity Toolkit 2014 after I upgrade labVIEW from 2013 to 2014?

Thanks

[mikeporter]

It's simple. Don't get any of them. There are free drivers that do a better job. Check

http://forums.ni.com/t5/LabVIEW/Extracting-one-column-from-Database/m-p/547276#M257531

You'll find the drivers on the last page, and a good discussion of why you don't want or need the DCT on the earlier pages.

Mike...

[crossrulz]

If you want to use the toolkit, you want to buy the current version.  That license will allow you to use older versions.  But you will want to download the 2013 version to use with your LabVIEW 2013.

[cliao]

 hi,  mikeporter

Your driver works well. However it seems it works well only with simple query, like select * from table. If I add criterial to the query, like select * from table where (((table.sn)="111111")), the following error showe up:

Error -2147217904 occurred at Exception occured in Microsoft OLE DB Provider for ODBC Drivers: [Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 1. in ADO Database Drivers.lvlib:Open Recordset+.vi->ADO Database Drivers.lvlib:Create and Read Recordset.vi->Untitled 1

This error code is undefined. Undefined errors might occur for a number of reasons. For example, no one has provided a description for the code, or you might have wired a number that is not an error code to the error code input.

Additionally, undefined error codes might occur because the error relates to a third-party object, such as the operating system or ActiveX. For these third-party errors, you might be able to obtain a description of the error by searching the Web for the error code (-2147217904) or for its hexadecimal representation (0x80040E10).

Chen

[mikeporter]

A couple things to try -- both having to do with the syntax of your query.

First, remove all the parentheses. They are unnecessary.
Second, you should be using single quotes -- or if the sn field is numeric you don't need any quotes at all.
Third, you can't have a table named table as that is a reserved word. This WILL throw an error.
Third, in this situation you don't need the fully qualified name a simple

sn='11111'

wiill do. This shouldn't cause a syntax error, which is what you got, but it's a bit cleaner.

Mike...

[cliao]

Hi, Mike,

Great. It works after change to single quotes. The reason I use double quotes is that I just copy the query form MS access. Access use double quote in query.

Thank you very much.

Chen