topic LabSQL Error in LabVIEW

LabSQL Error

lauraalkhoury — Thu, 26 Apr 2012 15:54:51 GMT

Hello all,

I am trying to connect to a database created by MS Access through LabSQL (yes, I know it's archaic and comes with no support but the LV Database Connectivity Toolkit just isn't an option on my student budget )

I used a connection string from www.connectionstrings.com/access-2007, and the string is as follows: Provider=Microsoft.ACE.OLEDB.12.0;Dbq=C:\Users\Laura\Simulation\Polar Bear Window & Door Manufacturing LTD\1500A Awning NFRC Report\W6- Awning 1500A.mdb;Uid=Admin;Pwd=;

The error message I am recieving is "Exception occured in Microsoft Access Database Engine: Could not find installable ISAM. in ADO Connection Open.vi->Untitled 1"

Attached is a snip of my VI for more info.

Thanks!

Laura

Re: LabSQL Error

nyc_(is_out_of_here) — Thu, 26 Apr 2012 16:09:07 GMT

Are there spaces in you mdb filename? If so, that may be causing the connection problem.

Re: LabSQL Error

lauraalkhoury — Thu, 26 Apr 2012 16:27:16 GMT

There were, but I deleted all spaces in the filename (and even the path to be safe), but still the same error!
I found this Microsoft KB article about the error: http://support.microsoft.com/kb/318161

Maybe you LabView experts can find a way to relate this to LabView!

Re: LabSQL Error

nyc_(is_out_of_here) — Thu, 26 Apr 2012 16:43:56 GMT

You are not using Jet.

Do you have Access 2007 installed?

Re: LabSQL Error

lauraalkhoury — Thu, 26 Apr 2012 16:54:32 GMT

I have Access 2003 (32 Bit) installed.

Re: LabSQL Error

nyc_(is_out_of_here) — Thu, 26 Apr 2012 17:47:33 GMT

Then your connection string is wrong.

You need the one for Access and not Access 2007.

Re: LabSQL Error

lauraalkhoury — Fri, 27 Apr 2012 16:28:42 GMT

Either way the provider is Jet 4.0, is it not?

Re: LabSQL Error

nyc_(is_out_of_here) — Fri, 27 Apr 2012 17:15:44 GMT

@lauraalkhoury wrote:

Either way the provider is Jet 4.0, is it not?

Uh, no.

Re: LabSQL Error

Dennis_Knutson — Fri, 27 Apr 2012 17:30:34 GMT

Instead of some connection string you found somewhere, create one from scratch with a udl or create a dsn in the ODBC Data Source Administrator. You can validate it there and know it is working before trying it with LabSQL.

Re: LabSQL Error

nyc_(is_out_of_here) — Fri, 27 Apr 2012 18:40:56 GMT

The connection string at ConnectionStrings.com are correct, but you have to know which one to use.