If I have not missed something in my description, I think that you can mislead the differences between the API and the library. Basically, ODBC is an API that is implemented as a library and is commonly used on computers running Windows through additional data access libraries such as ADO and ADO.NET. I mention this because you referred to unixODBC as a solution. This would not be a complete solution, as there would be more to it than just an API.
Simply put, a database file created using Microsoft Access is a flat .MDB file database (well, itβs a bit larger, but from the point of view of treating it as a database, thatβs all that matters here). If you know how the .MDB file structure works, you can write your own library that reads / writes to it. Of course, this is not trivial, but on Windows platforms it is provided by Microsoft using the libraries included in the OS. This is also called the JET driver and database. JET is a database format that implements a .MDB file and is used by Access and other applications using the appropriate JET drivers.
So, to find an equivalent option for platforms other than Windows, you need some kind of library that knows how to directly read / write to the .MDB file directly. If you are trying to use the .MDB file from the Access application at the same time, you need to make sure that the library of your choice supports simultaneous user access to the database.
In a quick search, there are some solutions that I can find. The first shows that this may have some functional limitations. The second is a commercial product.
MDB Tools
Easysoft Jet / Access Driver
source share