[plug] Help on Importing Access DB into MySQL

Steege, Phil E phil.e.steege at lmco.com
Wed Sep 18 22:32:55 WST 2002


I think I have enough to get started.
Thanks to all PLUG members for the inputs.

Phil

-----Original Message-----
From: Alan Graham [mailto:alan.graham at infonetsystems.com.au] 
Sent: Wednesday, September 18, 2002 9:59 AM
To: plug at plug.linux.org.au
Subject: Re: [plug] Help on Importing Access DB into MySQL


This is all well and good, but the major problem is not addressed by any of
these tools.

Unless you're an extremely unusual Access user, your database consists of a
lot more than a database schema and some data. Queries, Access forms, VBA
modules and reports are not touched by any conversion tool I've seen (if I'm
wrong and someone knows of one, *PLEASE* let me know. 
Quickly :-)

The conversion of a database schema and its data is a minor task compared
with rewriting the application that accesses it.  If you're happy to keep a
windows desktop, you can keep the Access forms, etc, and link the tables in
from the new DBMS.  But, from the tone of your mail, I don't think that's
what you want to do.

The only tool I know of that touches the client is a no longer maintained
Access to Delphi forms converter.  It only touches the forms, leaving the
VBA modules and any queries as an exercise for the reader, but it's a start.
You could then complete the redevelopment in Kylix. 
But this is a non-trivial exercise for all but the smallest Access apps.

Sorry if I sound negative, but you need to realise all the ramifications.

Having said all that, if this is an important app, moving the Access backend
db to a real DBMS is a very good thing.  I'd prefer PostgreSQL or SAP-DB to
MySQL (the lack of transactions is a killer, in my book), but any are better
than Access.  Access as a backend is... not good. 
Multi user db's are problematical at best.  The choice of what development
environment to use for the client will be... exciting.

One option is to get Codeweaver's crossover office and use it to run Access
as a front end, connecting to the new real DBMS backend.  That way, you get
the ease of use of your app maintenance, but a real DBMS to protect your
data.

Regards

Alan

On Wed, 2002-09-18 at 21:18, Jason Bainbridge wrote:
> Beat me to it and with a better alternative to boot. :-)
> 
> Just goes to show how useful google is especially if you know how to 
> feed it
> the right terms.
> 
> Regards,
> Jason
> 
> On Wed, 18 Sep 2002 21:05, Leon Brooks wrote:
> > On Wed, 18 Sep 2002 20:18, Steege, Phil E wrote:
> > > I want to be able to bring over an access mdb file and import that 
> > > straight into a mysql database on my linux box.
> >
> >     http://mdbtools.sourceforge.net/
> >
> > Cheers; Leon
> 
> 



More information about the plug mailing list