MySQL Forums
Forum List  »  Microsoft SQL Server

Re: New Migration Article
Posted by: Kerry Kurtz
Date: July 16, 2004 10:42AM

Mike Hillyer wrote:
> bob lambert wrote:
> > Mike
> >
> > Thanks for the info. Regardless if I choose
> > over MSSQL I am in for a lot of work
> converting
> > all the VB code behind my access 2002
> application
> > and forms am I not ?
Bob, actually, what you could do is keep your MS Access Application
Front End for deployment as you currently do, BUT Migrate the Back
End to MySQL and place it available to the web (even your home PC could be accessible to the web). And, with the proper migration of your back end
the only thing you "need" to do to the front end is to change how your
front end is linked (instead of native Access, it would be through ODBC
using the MySQL Connector/ODBC product) provided you are not opening
your own ADODB (or even DAO with ODBC Direct workspaces) connections
and recordsets (and do not use parameterized queries), your application
will work.
But, there are some caveats and consideration must be made to the type
of queries used for your forms, reports and such forth since MS Access will
break down your query and perhaps execute numerous queries to the server
and will then combine the data on the client and present the combination as
the recordset. Your best bet would be Migrate your back end, and then
determine what you can do to improve your application's performance.
I do have experience with this (one app that I converted the backend to
MySQL has approx 75 forms, 40 reports, 120 queries, 35 tables, and over
25,000 lines of code behind the forms and reports) and I still have not nailed
down one performance bottleneck I have (where, with the native Access back
end, it took less that 2 seconds for the report to start printing, it takes 20-50
seconds with the MySQL back end via Connector/ODBC, even as readonly
forward cursors).

Mike, you are right about this, and if he was going to migrate the
application to run on the web, I personally would recommend that
he not convert to ASP since it will use ADODB, plus, depending
upon how his applications forms are built, he will have also a very
great deal of other, additional, work/coding and then be limited
to using a hosting provider running (almost certainly) Windows and
IIS and generally end up possibly causing himself more troubles.
But I would recommend (if he was going to run the application
on the web) that he learn PHP and just redo his application using
his current code as his guide for the functionality (classes, functions
and so forth)

Kerry Kurtz

Options: ReplyQuote

Written By
July 08, 2004 12:30PM
July 09, 2004 10:18PM
July 12, 2004 08:30AM
July 12, 2004 10:33AM
July 12, 2004 10:41AM
Re: New Migration Article
July 16, 2004 10:42AM
July 17, 2004 03:58PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.