How to solve Labview 2016 (32bit) database error on Windows 10.

[Bob_Schor]

Sigh, same problem.  Here's the full error message:

NI_Database_API.lvlib:DB Tools Open Connec (String).vi->OpenaDBfile.vi<ERR>ADO Error: 0x80004005
Exception occured in Microsoft OLE DB Provider for ODBC Drivers: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in NI_Database_API.lvlib:DB Tools Open Connec (String).vi->OpenaDBfile.vi

I'm probably leaving for home, soon, but will check back here for any Words of Wisdom.

Bob "Chastened" Schor

[Justin2007]

Data Source name is not 'StationOne'. it should be  'SetupDatabase'. StationOne is the table name.

[Justin2007]

Your ODBC configuration has to be exactly the same as the attached picture. Thank you anyway.

[Bob_Schor]

Aha, that worked!  Now, at least, when I get home, I'll be less likely to mess up ...

Bob "Enlightened" Schor

[Bob_Schor]

OK, at home, I have two Windows 10 (x64) PCs, both with LabVIEW 2016 (32-bit) installed.  However, both PCs have Microsoft Office 2013 (64-bit) installed, not 32-bit.  When I open the 32-bit ODBC Data Source tool, the only native .accdb Driver is 64-bit.  I tried connecting to both the 64-bit and 32-bit drivers (for the 32-bit, instead of using the default .mdb extention, I specified "all files" and connected to the .accdb file.  However, when I then tried to open a single database, whether linked using the 32-bit or 64-bit ODBC Source, I got a LabVIEW error on the Open Connection function.  

Sorry, I haven't (yet) been able to duplicate your condition.  I may be able to build (in a VM) a situation with 64-bit Windows 10, 32-bit LabVIEW 2016, and 32-bit Office 2013, and if so, I'll run one more test.  Stay tuned (tomorrow) ...

Bob Schor

[Justin2007]

Thanks you so much, although it does not work yet.  

[Bob_Schor]

So it now works for me just fine.  Here's what I did:

I have a Windows 10 x64 VM at work.  LabVIEW 2016 (32-bit) is installed.  It had Office 2013 installed, but since I didn't know if it was 32-bit or 64-bit, I removed all of Office and reinstalled Office 2013, 32-bit.  Access was installed with "standard options" (I didn't add all the bells and whistles), along with Word, Excel, Powerpoint, and Outlook.

The first thing I did was open Control Panel, choose Admin Tools, and open ODBC Data Sources (32-bit).  I configured the three Access .accdb files as per your instructions.  I then opened each of them "by hand" to verify I could open them, and saved them back to disk.  I then ran your Database Test routine (I'm going to do it again -- four seconds later, it finished without errors, with the number "1010" showing as the (0,0) entry of each table.  I then opened OpenaDBfile, removed the Sequence structure, and Diagram-disabled the Wait.  This time, it finished in 2 seconds (reasonable, as it didn't wait 0.5 x 3 = 1.5 seconds).

So, now the code works for me.  Ingredients -- Windows 16 x64, LabVIEW 2016 (32-bit), Office 2013 (32-bit).

Bob Schor

[Justin2007]

That is great. Thank you so much. At least I know it is the software compatible issue. Now I have to figure out what is the problem on my windows 10 computer. Can you run it couple more time to confirm it is stable? Please see the error code that I have. I have ordered another win10 computer to check what happens.

Thanks again for your help

[Bob_Schor · Accepted solution]

As it happened, I just did re-run it, after modifying the code slightly to add three Array Size functions so I could tell you the sizes of the 2D arrays that were returned.  It ran fine, incidentally.  The sizes are:  Setup, 335x230.  User, 40x230.  Test, 509x230.

I'm going to shut off this VM, but I shouldn't need to "disturb" it for some time (days or weeks), so if you need me to check anything else, just let me know.  If you want to take this off-line, send me a Private Message on the Forums with your contact information (e-mail and phone) ...

Bob Schor

[Justin2007]

The Microsoft Access on the windows 10 computer is 2016 (32bit). I think that is the only different, comparing with yours. I will requst Access 2013 software and try again.

Thank you very much.