You did not mention, but I assume that your AutoCAD 2015 is 64-bit. That is, your Access DB data access issue is due to AutoCAD being 64-bit, not being 2015.
The VBA code in your AutoCAD is now running as 64-bit process since AutoCAD 2014, if the AutoCAD is 64-bit. Prior to AutoCAD 2014, even AutoCAD being 64-bit, its VBA is still 32-bit. So, your existing VBA code is OK with AutoCAD 2013 or older, be it 32 or 64-bit.
If you have to use the existing code for AutoCAD 2014 or later without significant update, you need to use 32-bit AutoCAd2014/15.
If you have to make your existing code work with 64-bit AutoCAD (2014/15...), then modification/update of some sort is inevetable, depending on your choice of investment you can put into. Here are a few advices I can think of:
1. Install 64-bit MS Access data engine, which replaces the older Jet Engine since Access2007. There has been some issues difficulties of doing this.
- If you or some of your uses use Office 2007. It is very likely the office suite is 32-bit. In this case, the 64-bit MS Access Data Engine cannot be installed in the same computer. So, the only option here is to use 64-bit Office 2007, which may open another can of worms..
- if you and your users use MS Office 2010 or later (again, it is usually 32-bit suite, as MS recommended, even the computer is 64-bit), then yes, you can install MS Access Data Engine 64-bit. But the 64-bit MS Access Data Engine must be installed prior to MS Office suite (be it with MS Access or not). This is at least true for MS Office 2010. I am not sure for later MS Office, because I no longer dealt with MS Access for quite a while. This could be a troublesome: just because of your AutoCAD need, many of your usersè computers have to get MS office uninstalled for installing MS Access Data Engine 64-bit and then reinstall. Here is a link that may help you:
http://blogs.rand.com/architectural/2011/12/by-joe-eichenseer-how-many-of-you-have-run-into-this-and...
This approach should work if the MS Office installed is without MS Access (32). But if the MS Office includes 32-bit Access (which installs MS Access data engine 32-bit), I am not sure if it would break MS Access Data Engine 64-bit. Youèd better try it with a test computer.
OK, with MS Access 64-bit Data Engine installed, now you can code data access with ADO2.x (2.8 is the latest) iin 64-bit AutoCAD VBA. I hope your code uses ADO, not DAO (not sure if it works with MS Access Data Engine, DAO is too old technology for me to touch is again in last 10 years). Ièd imagine your data access code may need minor update if you used ADO, at most.
However, since AutoCAD VBA is 64-bit, even your data access code works again with MS Access Data Engine 64-bit installed, it does not mean your other VBA Code in AutoCAD also works. If you have complicated UI (user forms) in your AutoCAD VBA code and used some controls/components that are 32-bit only, then your code will still not work and you must replace these controls/components with 64-bit version, which may often not available at all.
So, depending on the nature of your Acad VBA app, using MS Access Data Engine 64-bit may solve the data acess issue, but your Acad VBA may still not work with AutoCAD 64-bit VBA.
2. Moveing your data to a database server, so that you can code data access in Acad 64-bit VBA without having to depend on MS Access. For example, you can move the data portion of yoru MS Access database into SQL Server (you can use the SQL Server Expresss, whichis free). in this case, you keep your MS Access UI/Code iin MS Access as frontend application, which connect to the SQL Server database. Your MS Access application as fronend may only need very minimum modification. In fact, if your exing MS Access app has been designed well, it is supposed to be split as front and back end already.
Again, with this approach, in your AutoCAD VBA side, since it is 64-bit, your existing VBA code may still not work if it uses 32-bit controls/components.
3. Forget AutoCAD 64-bit VBA. Due to the lack of support to 64-bit VBA (not many 64-bit controls/components available as with 32-bit), keeping doing VBA development in AutoCAD may not be worth the effort. You may want to start porting AutoCAD application to its .NET API.
HTH
