I'm seeing more and more people complain about these things. None of the "solutions" are perfect, and some are lots of work - usually in a inverse-relationship.
Here're the solutions I've seen so far (listed from least work and least possibility of success):
(1) The issue with such "hacked together" driver is that it needs to be done to each workstation. And of course could easily be messed up on one or more through a slight mistype / some other setting which might differ.
(2) Could you perhaps use DotNet to connect to the DB? I think the DotNet connections don't worry about 32/64 bit incompatibilities. You could add some lispfunctions in your DotNet DLL so your lisps handle the DWG and UI interaction with ACad, and the DLL only handles linking, sending & retrieving data from the DB.
(3) Or could you translate your DB from Access to something else? If you don't want to install a server on a dedicated machine and want to stick with a normal file based DB, then you could try using DBase / Paradox files instead - there are ODBC drivers for those, and (especially DBase) has many import / export filters in nearly all programs.
(4) Or try SQLite through nullptr's awesome tool:
http://www.theswamp.org/index.php?topic=28286.45(5) I'd avise using a true DB Server instead of Access (or some other file-based DB) if you're going to have more than one person linking to it at once (I've had numerous issues with corrupt MDB files due to multiple concurent edits). Perhaps try something like
Ms-SQL Server Express, or
MySQL, or
PostGre, or
FireBird, or any of a number of
others (I prefer PostGre / FireBird as it's Open Source and free, has more control than even MS-SQL, and can run on any operating system {Win/Linux/Mac/BSD/Unix} - so the "server" could be some old PC brought to life again).
Note that even Access can be used as the client side into any of these DB servers - so you could still use the forms / reports / queries you've built in Access to work with your data. It's just that your tables would be linked tables instead of directly saved into the MDB file. Or you could use LibreOffice Base instead of Access, as its got native drivers for most of these as well as ODBC / JDBC drivers if not native - another free program which runs on any OS.
