Arthur Fuller
fuller.artful at gmail.com
Wed Jul 11 19:16:46 CDT 2007
For what it's worth, anyone interested in MySQL is invited to visit my co-authored e-book at www.artfulsoftware.com. Arthur On 7/10/07, Rocky Smolin at Beach Access Software <rockysmolin at bchacc.com> wrote: > > That looks real helpful. I think that SQL is overkill for my market > segment, but this is coming from a potential distributor in Singapore who > thinks otherwise. So if the market is there, I guess I'll dive in. > > Rocky > > > > > > > > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of F Kay > Kendrick > Sent: Tuesday, July 10, 2007 12:15 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] FW: [AccessD] Converting to MySql > > Rocky, > > >From http://www.kitebird.com/articles/access-migrate.html#TOC_2: > ...if you install the MySQL Connector/ODBC driver (formerly known as > MyODBC), Access can make ODBC connections to MySQL servers over the > network. > You can still use the contents of your tables through Access, but the > tables > themselves are hosted by the MySQL server. > > The MySQL Connector/ODBC driver can be downloaded from > http://www.mysql.com/products/connector/odbc/. There is also a migration > toolkit available from > http://www.mysql.com/products/tools/migration-toolkit/. > > HTH, > > Kay > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Rocky > Smolin at Beach Access Software > Sent: Monday, July 09, 2007 6:25 PM > To: dba-sqlserver at databaseadvisors.com > Subject: [dba-SQLServer] FW: [AccessD] Converting to MySql > > > > > Copied from the AccessD list. I think this question is more appropriate > here. > > Rocky > > > > Rocky Smolin at Beach Access Software wrote: > > Dear List: > > > > I have a request to make my manufacturing package compatible with > > MySql. I use some bound forms, and a lot of DAO. The app is split > > FE/BE with linked tables pointing to the BE. I also allow the user to > > select the BE they want so they can run multiple BEs if desired. > > > > What would be involved in doing this? Would it be enough of a rewrite > > that it would require a separate product? Or can the current product > > be made 'switchable' between an Access BE and a MySql BE? > > MTIA, > > Rocky > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.476 / Virus Database: 269.10.2/893 - Release Date: 7/9/2007 > 5:22 PM > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > >