Re: [Sheflug] Re: Access to MySQL

[Matthew Palmer <mjp16 [at] xxxxxxxxxxxxxxx>]

On Sun, 15 Jun 2003, Richard Ibbotson wrote:

> > Define "convert" exactly, in these circumstances.  There are several levels:
> 
> Just now it's an Access database.  The owner wants to have it
> converted to MySQL.  Presumably I can use the MySQL ODBC app so that
> M$office can connect to MySQL.

Again, define convert.  If all you've been asked so far is "convert this
access DB to MySQL", then you need to go back to your paymaster and ask the
questions I have.

> > * Data stored in MySQL, existing Access application for front end;
> 
> Could be.

This is the most likely course, because Access is relatively decent for
building a UI if you only need to cover the basic end of the spectrum.

> > * Data stored in MySQL, Access for front end but migrating to something else
> > (GNUe, some Webapp, or whatever) over time;
> 
> This looks good but probably requires a lot of work.

A hell of a lot.  You'll get this when the company is looking to expand and
maybe wants to get a web-enabled version of their system out to the masses
(or even just road warriors).

> > I'm in an ongoing project to do the second of those options at present.
> 
> Oh... good news :)

Well, that's *one* way of looking at it... <g>

> > If you're going with option 1, you can do a simple outload, relink all the
> > tables, install MyODBC on all the windows clients, and collect your cheque.
> 
> Probably the best thing to do.  Get out before something else comes
> up. :)

Oh, if you're being paid by the hour it's an absolute score to totally
rewrite the app.  It takes a pile of time, but most of the piss-farting
around (writing specs and whatnot) is gone because they just say
"reimplement this".  Very boring, though.

- Matt


___________________________________________________________________

Sheffield Linux User's Group -
http://www.sheflug.co.uk/mailfaq.html

  GNU the choice of a complete generation.