[dba-SQLServer] Upgrade to MySql

There are a few good reasons for not going to MySQL. 

For example you can not roll back a transaction or series of transactions.
For any application, that is at all like accounting, that is a big minus. 

Just because bound MDB applications get away with it does not mean that it
is acceptable in the business world. Of course that is why a programmer uses
ADO for data connection. (ADO has full BeginTrans, RollBack and Commit
functionality but you must have the appropriately matching BE DB like MS SQL
Express, PostgreSQL, Oracle Express Edition etc...)

Jim

 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mark Breen
Sent: Thursday, August 12, 2010 4:34 AM
To: Discussion concerning MS SQL Server
Subject: Re: [dba-SQLServer] Upgrade to MySql

Hello Rocky,

What are the benefits to the client of mySQL over Microsoft SQL Express ?

Thanks

Mark


On 8 August 2010 16:25, Rocky Smolin <rockysmolin at bchacc.com> 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
>
>
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com