Access -> mySQL

We have an existing Access database that we want to provide web access to. We're likely going to convert the database to mySQL, run an Apache server, etc.

My question is about the existing front end for the database. After the conversion, will the existing programs we've written work as-is against the mySQL database? We have a combination of about 12 Access 95 machines and five Access 2000 machines that hit the database internally.

My vague impression upon first glance is that once we get it pointed at the new database, probably using an ODBC front-end, that it should "just work." Does that sound reasonable?

TIA,
Drake Christensen

Depending on how the front end is programmed, Maybe. I have not work with MySQL, but I know that when moving from Access to SQL Server, it isn't always that clean. It all depends on how the front end was programmed. You will have to set up a test enviroment and give it a try and fix erros as you go.

Maybe someone else has tried this upgrade.

S-

Well, sure, I understand that "it depends." That's the whole point of this thread. I guess my question can be restated as: What are some of the common problems with trying to do that? Are there particular queries or posting commands or conventions that are known not to work? Especially anything that might be used fairly often?

For example, I saw one thread that mentioned differences in generating a unique ID number in SQL vs Access. Would that require a programming change everywhere a new record is inserted into those tables?

Anything else similar to that?

Also, from skimming around, it appears that an ODBC front-end is the most seamless way to get at the new database from Access. Is that correct, or are there other viable alternatives I should be considering?

Drake