ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabSQL Error

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 Smiley Tongue )

 

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

 

 

Download All
0 Kudos
Message 1 of 10
(4,408 Views)

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

 

 

0 Kudos
Message 2 of 10
(4,399 Views)

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!

 

0 Kudos
Message 3 of 10
(4,396 Views)

You are not using Jet.

 

Do you have Access 2007 installed?

0 Kudos
Message 4 of 10
(4,387 Views)

I have Access 2003 (32 Bit) installed. 

0 Kudos
Message 5 of 10
(4,381 Views)

Then your connection string is wrong.

You need the one for Access and not Access 2007.

 

 

Message 6 of 10
(4,376 Views)

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

0 Kudos
Message 7 of 10
(4,353 Views)

@lauraalkhoury wrote:

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



Uh, no.

0 Kudos
Message 8 of 10
(4,346 Views)

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.

0 Kudos
Message 9 of 10
(4,343 Views)

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

 

 

0 Kudos
Message 10 of 10
(4,339 Views)