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

[Bob_Schor]

Can you attach a simplified Access Database (unlocked, of course) and a note naming the Tables you are trying to open?  I have LabVIEW 2016 and Office 2013 installed on Windows 10 at home, and would be happy to "experiment" to see if I can (a) duplicate your problem (describe the process in sufficient detail that I could code what you are trying to do) and (b) possibly find a work-around or an outright "fix".  As it is not yet noon here, you have a few hours to respond (but it will also take a few hours before I can get to this ...).

Bob Schor

[Justin2007]

Hello Bob,

I Please see the attachment. before you try out the software on Windows10, Please follow the image file in the attachment to configure the DSN connection. Thanks a lot for helping me.

Steven

[Justin2007]

This is the attachment

[Bob_Schor]

OK, Justin, I'm still at work, and can open your attachment.  Before I leave, I want to be sure I can open things and understand what you need to do.  Some comments:

• I cannot directly open the three test Access databases -- they all require a Password.
• If I open the ODBC Data Source Administrator, it already has MS Access Database (*.mdb, *.accdb) as a User Data Source.  Should I "add" another one?  If so, how should I configure it?  Is there a Data Source Name I should select?  [I don't have your code open -- presumably you've chosen names there ...]  I see a "Select" button for Database -- I presume I navigate to one of the three you provided (I just tried it, and connected to Setupdatabase.accdb).  Do I leave System Database alone?  Are the default Options OK?  [Note -- I just did this, calling it Test1, and it now appears on the ODBC list of User Data Sources, which is probably the Whole Idea].
• Now I think I see the situation.  OpenaDBfile is the routine to handle each of your three DB files, with DSN names TestRecordForStation1, UserName, and StationOne.  I'm guessing these correspond to the "real" Access files TestRecordDataBase, UserNameDataBase, and Setupdatabase (in that order), correct?  Ah, and perhaps the passwords are SetupPassword, UserPassword, and TestRecordPassword -- just a second, I'll check ...
• Yes, never mind the question about the Passwords (at least for SetupPassword, didn't check them all ...).  I should now be Good to Go, and will definitely test this out tonight.

Bob Schor

[Bob_Schor]

Aha!  Just to make sure I'm Good to Go, I tried OpenaDBfile with the StationOne parameters, and got Error -2147467259.  I'm largely sure that this is because I've not installed the DB Connectivity Toolkit, so while I have a little time here at work, I'll give that a try (I'm on Win7 here, which you already said works -- the test will be on the home Win10 machine(s)).  If you don't hear me whining, assume that was the problem ...

Bob Schor

[Bob_Schor]

Oops, that wasn't it -- there is no "Database Connectivity Toolkit", and I've got the Database functions in my Palette.  Let's try a reboot to get the ODBC connections firmly established ...

BS

[Justin2007]

Thanks for trying the software. It works on Windows 7

[Justin2007]

The attachment in my previous comment shows how to configure the ODBC link.

[Bob_Schor]

---

@Justin2007 wrote:

The attachment in my previous comment shows how to configure the ODBC link.

---

Yes, and I did exactly that.  It seemed to work, but now that I rebooted and go back in, the Microsoft ODBC Administrator says "The setup routines for the Microsoft Access Driver (*.mdb,*.accdb) ODBC driver could not be found.  Please reinstall the driver".  I'll do a bit of Web research and look for what I forgot (maybe there's a piece of Office that is missing ...).

BS

[Bob_Schor]

OK, so it's an issue between 32-bit LabVIEW, 32-bit Office (which is what I have here -- I'm pretty sure I've got 64-bit at home), and 64-bit Windows 7.  Let me open the ODBC routine on WOW32 ... Yep, they are there, and the configuration looks OK.  Here's StationOne.

Note that I've set no Advanced Options -- in particular, Login name and Password are both blank.

Wait a minute -- I recall, now, when I opened it "by hand", a message popped up saying "Some Options have been disabled" (or something like that, a Security thing).  I'm going to try to clear that and see if that fixes things ...

BS