RE: Access VBA Migration
"Bill White" <[email protected]>
| Newsgroups | gmane.comp.db.mysql.mycc |
|---|---|
| Organization | PC Crisis Line |
| Message-ID | <[email protected]> |
I've used Access since version 2 and now use 2003 and PHP/Mysql. That is an accurate assessment of the problem. As an interim step you can continue to use the Access front end for forms and reporting and use ODBC to Mysql on the back end. -- Bill White home: [email protected], 650-961-4837 office: [email protected], 650-691-2022 http://billwhite.us/ -----Original Message----- From: Gregory L. Magnusson [mailto:[email protected]] Sent: Tuesday, June 14, 2005 12:49 PM To: [email protected] Subject: Access VBA Migration Hello all, I am wondering, can anyone comment on the following statement regarding migration of Access applications out of Access? "The biggest problem with migrating from Access to some other database isn't the database data itself (the tables, data, and separate queries), it's the fact that people have used it to create applications; Access includes a built-in VBA runtime that people use to create forms and create reports. Many of the queries and updates are "bound" to controls on the forms. It's those forms, bound queries, and reports that get lost when you migrate an Access application out of Access--and I don't think MySQL has done or can do anything to solve that problem. " Any and all information will be appreciated, Greg Magnusson [email protected] -- MySQL GUI Tools Mailing List For list archives: http://lists.mysql.com/gui-tools To unsubscribe: http://lists.mysql.com/[email protected] -- MySQL GUI Tools Mailing List For list archives: http://lists.mysql.com/gui-tools To unsubscribe: http://lists.mysql.com/[email protected]