Issues using MS Access as a front-end to a MySQL database back-end?

http://bit.do/dSPa5 Secret sale page at EasyFrom.
Two users wanted to share the same database, originally , written in MS Access, without conflicting with one , another over a single MDB file. , http://www.mysql.com/products/tools/migration-toolkit/ , Migration Toolkit, I moved the tables from a simple MS Access database , to MySQL using its (which works well, by the way) and , set up Access to link to those tables via ODBC. So , far, I've run into the following: You can't insert/update/delete , rows in a table without a primary key (no surprise , there). AutoNumber fields in MS Access must be the , primary key or they'll just end up as integer columns , in MySQL (natch, why wouldn't it be the PK?) The tables , were migrated to MySQL's InnoDB table type, but the , Access relationships didn't become MySQL foreign key , constraints. Once the database is in use, can I expect , any other issues? Particularly when both users are , working in the same table? . Programming help. Powered by MaryTTS. cc-by-sa 3.0 Attribution: Stack Exchange Network, follow the links for updated information Question : http://stackoverflow.com/questions/5842, By yukondude : http://stackoverflow.com/users/726, Answer : http://stackoverflow.com/questions/9200, By onnodb : http://stackoverflow.com/users/1037