Stuart McLachlan
stuart at lexacorp.com.pg
Sun Aug 8 20:15:02 CDT 2010
If you are happy to go with ODBC linked tables, it's simple - just create a MySQL database with the same tables and link to them instead of the Access tables. It's quite possible that that is all you need. Try it and see whether there are perfomance problems - if so, you will need to look at optimising your data sets with views and pass- through queries. FWIW, I've used Access FEs with OBDC connections to SQL Server and/or MySQL in a number of cases and have not experienced any performance problems to date. -- Stuart On 8 Aug 2010 at 8:25, Rocky Smolin wrote: > > Dear List: > > I have a client with a rather large application who is considering > upgrading the back end to MySql. > > Objects: > ~100 forms > ~150 queries > ~75 reports > > Lots of code modules with many lines and lots of CBF. > > The app uses bound forms and lots of DAO. > > BE is an mdb. FE & BE are both A2K3. > > Question is, of course, what is involved in converting this front > end to > work with a MySQL back end? > > MTIA, > > Rocky Smolin > Beach Access Software > 858-259-4334 > www.e-z-mrp.com ; > www.bchacc.com ; > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > >