mysql and access

[gruntly-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org (Theodore Ruegsegger)]

Stephen wrote:

> At work, one of the people
> here setup an MS access database application which is quickly turning
> into a nightmare because it does not use a real database as a back end.
> So I'm thinking that perhaps I can help them by setting up some tables
> in my mysql database server I have running which would ease up the data
> entry problems they are having. So the question is, is it feasible to
> have a mysql database running on Linux be used as the back end to a MS
> access database application running on windows? If it is, any gottachas
> that one needs to be careful of?

It would never have occurred to me to set up a MySQL (or PostgreSQL)
backend yet still retain Access as the front-end, but no doubt you
have your reasons.

I have, on the other hand, migrated numerous business applications
from Access to GAPP (GNU/Apache/PHP/PostgreSQL) architectures and can
probably help with a problem you'll soon encounter: migrating Access
data to a different DBMS. Unless Microsoft recently fixed it (and why
would they?), the export feature in Access is broken.

Details, and a workaround, are at:
http://www.tux.org/~tbr/database-conversion/
more specifically,
http://www.tux.org/~tbr/database-conversion/#Microsoft

Granted, I haven't had occasion to use the cited scripts in years, so
you may find you need some changes (feel free to email questions or
fixes) but in general they should do the job. And of course, since
you're importing the data to MySQL rather than PostgreSQL you'll need
to make some syntax adjustments.

Speaking of that, If you happen to write a html2mysql.sh script that
does for MySQL what html2pgsql.sh does for PostgreSQL, please share
and I'll be happy to add it to the webpage and give you credit.

HTH
Ted

ps. If you happen to discover that the Access export feature is no
longer broken, please let me know!
tbr