32-bit Database Toolkit in 64-bit LabVIEW

[BrittonB]

I am using 64-bit LabVIEW 2018 and I am trying to connect to a database built in 32-bit Microsoft Access (database_name.accdb) using the 32-bit Database Toolkit.
I understand that the 64-bit Database Toolkit just entered Beta for LabVIEW 2019, but that is not an option for me.

Copying the 32-bit Database Toolkit over to the 64-bit LabVIEW folder (following this advice from Brian_Powell) fixed all the broken run arrows for my database VIs.
But I still cannot open a connection to the database. I get an error that the Provider cannot be found.

The issue seems to center on 64-bit LabVIEW trying to run the 32-bit dll, oledb32.dll.
Following the instructions for 64-bit systems here, I was able to make a .udl that recognized the Microsoft Office 12.0 Access Database Engine Provider and could pass a test connection.
But if I tried to call that .udl from LabVIEW or just open it without using the command line rundll32.exe, it would error out, claiming the Provider could not be found.

How do I enable 64-bit LabVIEW to open a 32-bit database connection?

-Thanks

[altenbach]

I guess using 32bit LabVIEW is not an option?

[BrittonB]

Unfortunately, 32-bit LabVIEW is not a option.  

[billko]

I don't know anything about the toolkit, but if it uses a dll (which would be a 32-bit dll) you are dead in the water.

[ijustlovemath]

We use 32-bit LV precisely because it has wider support of things like databases.

[aputman]

I'm going out on a limb here because I have never used 64bit LabVIEW for these reasons.  My guess is that it won't work...in which case you are probably out of luck. 

Open odbcad32.exe in c:\windows\syswow64 and create a user DSN that will connect with your database.

Then create a UDL file on the desktop, and select the OLE DB provider for ODBC Drivers.  Configure OLE connection using the DSN that was created in the last step. 

Are you able to establish the connection or not?

If so, edit the UDL file with a text editor and copy the connection string.  Use this string on the DB Tools Open Connection VI. 

The thought (and probably a bad thought) is that adding another layer (ODBC) in between LabVIEW and the database might convince it to work.  I'm not sure if you need odbcad32.exe for the SYSWOW64 folder or the system32 folder but try both if the other doesn't work. 

[Adolfo.Islas.ReckonSoluti]

I remember one time has this issue in the past my solution as i remember was.

1.take the DB toolkit of 32Bits and paste in 64 bits folder

2.open a new project and execute a mass copile in the library again 

3.- using this new VIs instead of the DB toolkit VIs

I dont Remember if this solve the issue totally, but maybe works, if you want tryit go ahead.

😉