[plug] Help on Importing Access DB into MySQL

[Alan Graham]

Yeah I saw this one a while back but the up front cost ($US 695 to
convert to Java, $US395 to VB for each 30,000 lines of code) didn't hurt
as much as the very restrictive license.  I have one app running at four
client sites.  These guys wanted each of my clients to pay for a full
license, as well as my paying for the license.  Considering the
inevitable rework that would have to be done (no conversion tool is ever
completely correct) this is unbearable.  

Alan

On Wed, 2002-09-18 at 22:50, Jason Bainbridge wrote:
> How do you feel about Java?
> 
> http://www.diamondedge.com/
> 
> Have what looks like a pretty good conversion tool that goes the whole hog and 
> even converts the reports into Crystal Reports. Expensive though (US$395 per 
> license), the free trial will only convert the northwind.mdb as well so 
> that's pretty useless. 
> 
> Although one wonders how the checking on the free trial is implemented, 
> wouldn't really surprise me if you just had to rename your database to get 
> around it. Kinda like Partition Magic 7 with it's "You have entered an 
> in-correct serial number, do you wish to continue?", click yes and it 
> installs. Classic...
> 
> Cheers,
> Jason
> 
> 
> 
> On Wed, 18 Sep 2002 21:58, Alan Graham wrote:
> > 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
> 
>