Link to home
Create AccountLog in
Avatar of TimSledge
TimSledgeFlag for United States of America

asked on

MS Access 2013 Linking to SQL Tables - DAO No Longer Works

Years ago I created an MS Access application that dynamically links to SQL tables for one of my clients.   The client has upgraded his computers to Windows 8 64 bit with MS Office 2013 64 bit.

The attached code used DAO to dynamically link the Access application to a list of SQL tables stored in an Access table.

I need to replace the DAO with something that will work with Access 2013.  Any code snippets would be appreciated.

Thanks,

Tim Sledge
DOAToConvert.txt
Avatar of Jim Dettman (EE MVE)
Jim Dettman (EE MVE)
Flag of United States of America image

What doesn't work?  It should work fine as long as you referenced the DAO lib.

Jim.
Avatar of TimSledge

ASKER

DAO is not supported by MS Access 2013.
ASKER CERTIFIED SOLUTION
Avatar of Jim Dettman (EE MVE)
Jim Dettman (EE MVE)
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
No, it is not a web database.  I changed the reference from DAO 3.6 to Microsoft Office 15.0 Access database engine Object, and now that I think about it the DAO lines do compile.

However, the SQL tables will not link using the DAO code.

This is MS Office 2013 64 bit.  I'm wondering if this could be about a driver.  I've heard there are problems using MS Access 2013 in the 64 bit version.
I'm wondering if I need to change something in the line below.
 
tdf.Connect = "ODBC;Driver={SQL Server};Server=" & strServerName & ";Database=" & strDatabaseName & ";UID=" & strUserName & ";PWD=" & strPWD
When I try to run the code to link the SQL tables I get the error message:  "Could not find installable ISAM.3170.
<<This is MS Office 2013 64 bit.  I'm wondering if this could be about a driver.  I've heard there are problems using MS Access 2013 in the 64 bit version. >>

 Yes, there are problems in that because it is a 64 bit app, it is going to make 64 bit calls.  You you need 64 bit ODBC drivers, API calls need to be modified, etc.

  But 64 bit ODBC drivers should be part of the OS, so exactly what is the error/issue that your seeing?   And what version of SQL are you trying to connect to?

Jim.
Disregard the "Could not find installable ISAM 3170" comment.  That happened only when I removed ODBC from the connection string.
More info...

I can override the startup code and open a form I created to start the code that links the SQL tables (SQL 2005), and it works.

I think  I was using a startup macro to run the linking code, but I can't find Macos in the Access 2013 Object list.  Does Access 2013 still use Marcos?

I think the problem is that I had a macro set to run on startup that loaded the SQL tables, but the macro is not running in Access 2013.
<<Does Access 2013 still use Marcos?>>

 Yes, macro's are still available and work the same as before.  The navigation pane is a bit different to work with then the old database container if your coming from Access 2003 or earlier.

  My sure you click "All Objects" to see everything.

Jim.
Learning that the "Microsoft Office 15.0 Access database engine Object" contains the DAO model reference was crucial to my finding the solution to my problem.  However, it was only the first step.

Something in Access 2013 was handing some of my code differently that in Access 2002.  I did a code workaround and got it working.

Thanks for your dialogue and help.

Tim Sledge
You'll find that Access 2007 and up want things done in a very specific way sometime over past versions.

As part of building out web databases and adding to macro capabilities, it seems Microsoft tightened up on the way VBA and Access interact.

Jim.
After Access 2007 was introduced I moved almost exclusively to developing ASP.Net/SQL Server applications so I have not kept up with my MS Access skills.

Thanks again for your help.