<ph**************@gmail.com> wrote in message
news:11**********************@g44g2000cwa.googlegr oups.com...
But that would only mean that it would allow for an import of a .mdb
file, right? Windows isn't necessary for that, just for allowing it to
interface with Access. And I thought OpenOffice has an Access
equivalent coming out.
http://dba.openoffice.org/ says:
"There is an alpha version of a MDB driver available. It currently has
read-only support for Access 97 (Jet 3) and Access 2000/2002 (Jet 4)
formats."
I wouldn't rely on such a bleeding-edge tool for business-important data.
And it's read-only anyway, so you can't transfer MySQL to .MDB -- in other
words, you don't gain anything over using the MySQL Migration Toolkit.
Anyway, I'm not sure how one could read an MS Access database that resides
on a Windows machine, by running any sort of application on Linux. Somehow
the Linux application would need to connect to the Windows host over the
network, and gain read/write access to the MDB file as a database. MS
Access doesn't implement a cleint/server interface for data access; it's a
GUI application that reads and writes MDB files local to the host running
the GUI, or at best on a network-mapped drive.
I don't know of a good solution for offering automatic bidirectional
synchronization between MySQL on Linux and MS Access on Windows.
A different solution might be for your boss to use MS Access forms as a
front-end to a MySQL database residing on her Windows XP laptop. Then you
could use MySQL Replication features to keep the two MySQL databases
synchronized.
Regards,
Bill K.