Plugin crash
With the current state of technologies related to AutoCAD use, using Access Database for data storage would be possibly the worst among many viable choices, IMO, especially when the CAD computer has 64-bit AutoCAD but also stuck with old MS Office suite (2007 and 2010).
It looks like you have already figured out how to painfully get Access DB Engine installed in computer with Office 2007 (uninstall Office, if it somehow already there; install Access DB engine 64-bit; reinstall Office suite back; and if the Office suite must include MS Access and is 32-bit, then you cannot install Access DB Engine 64-bit...what a burden!). Also. good for you that you were able to make things a bit easier by install Access DB Engine in "passive" mode, which may not be succeed with newer Office version: I tried with my Office 2016 installed computer without success a while ago.
From your description, it is difficult to say where the problem could be. Reporting the error to Autodesk would not help at all, because it is your own code causes the error, and most likely related to the use of Access DB Engine for accessing data in *.mdb/*.accdb file. You should take advantage of .NET language's structured exception handling (try...catch...) to catch as much as possible exceptions, so that you can easier to tell where the exception comes from.
Another way to tell, at least, whether the Access DB Engine is installed and works or not, is to use "Control Panel->Administrative Tools->Data Sources". Then try to create an ODBC data source that connects to an *.mdb/*.accdb file. During the process, you should be able to select MS Access DB Engine as provider and eventually test if the data source connection is OK or not. If you cannot succeed creating the data source, that means the Access DB Engine is not installed, or not installed correctly, hence your AutoCAD plugin does not work.
Again, as I said, at current time, using Access DB Engine is the worst one among many choices. If you want to have shared data storage, you can use free SQLServer Express (or other DB server, such as MySql...), if the data is for single computer use, you could use file-based SqlLite...If your data access code written with ADO.NET well enough, it is fairly easy to switch data from Access DB into, say, SqlServer(Express), with only minor code change.
SQL Server and similar have a lot of overhead for management, as well as potentially having to fight IT for various access rights, setting it up on the server, and so on. Not that Access is always the best choice either, as it's overkill for relatively small amounts of data (which may be better served by XML or even CSV) and is vulnerable to IT applying system updates or upgrading to a newer version. But Access is still a decent choice for that middle ground where you need a file-based, network-located, query-able database which may have additional links to Excel or other systems.
From experience, Office 2010 x32 doesn't play nice with the x64 Access engine. Later versions of Office using the ACE OLEDB connection work better. But I'd recommend installing the x64 version of Office for CAD users so there isn't any buggering around.
Yes, there's "recommendations" out there that no one uses x64 Office. Those are based on a "white paper" which only points out that there may not be x64 versions of custom controls, so previous customizations may not work. It does *not* recommend against using x64 Office. We've been using x64 Office (on both CAD and non-CAD computers) for some time.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you insist on using, or have to stick with, Access database, your best bet to avoid the hustle of installing 64-bit Access DB Engine (because AutoCAD VBA is 64-bit, assuming using 32-bit AutoCAD is not an option) is to use 64-bit MS Office suite (or not us MS Office application at all. again, probably not an option), as @dgorsman suggested.
That is, choose one from these 2 options: all users have 64-bit MS Office apps; or do not use Access database with your AutoCAD app.
