bob lambert wrote:
> Mike
>
> Thanks for the info. Regardless if I choose MySQL
> 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 ? I guess all that code would
> end up on the server side of the equation, but I
> am confused as to where it goes - I mean now its
> carried along in my access db and neatly tied to
> individual forms. If I leave that (and
> essentially leave MS-dom), what s/w do I use and
> how do I collect/manage it all ? Does MYSQL have
> a similar s/w interface to do the equivalent of
> all the VB code I wrote in Access, and what
> language is it ? Or do I have to buy some other
> s/w ? (I do have vb.net std at home now).
>
> Thanks a bunch
> Bob Lambert
You are right Bob, no matter what database you choose you are going to have a lot of work migrating your existing application to the web. That being said, any functions you wrote in VB could possibly be migrated to ASP without much effort, so if you used reusable functions and classes you will be ahead. You could use VB.NET and ASP.NET with either MSSQL or MySQL, and try to import as much of the code as possible. MySQL has no built in programming interface, but there are languages such as PHP available which work well at exposing MySQL data (or SQL Server data for that matter) to the internet.
Mike Hillyer, Technical Writer
MySQL AB, www.mysql.com
Office: +1 403-380-6535
Blog:
http://www.openwin.org/mike
"The Open Source movement has become a major force across the software industry, and MySQL is the world's most popular open source database."
--Fortune Magazine