You didn't mention whether they are planning on keeping the NT box, but I assume that they are, and that what you want to do is leave the Access app working, but point it to the Linux-MySQL QUBE. I have been there and done that (well, except for the QUBE part -- I run Mandrake 8 on an old P-233.
I second the choice of DB Tools. There are other tools with import wizards but this one works very well. The only problem is that neither DB Tools nor any other similar tool that I came across is capable of importing the index information. All you get is the data. In one of my apps there are 400+ tables, and it's a considerable pain to have to manually create the indexes. However, there is a Windows-based shareware tool called dbScripter (from DKG Advanced Solutions). It only costs something like $50 US for the full version. I may have the price wrong since I bought it a couple of years ago (and have received two or three free updates since). dbScripter doesn't do direct imports. As the name implies, it generates scripts which you can run to achieve the same end. It breaks down a job into 3 possible scripts: structure, data and indexes. It works with profiles so that you can direct it to change a currency or yes/no column to the appropriate MySQL data type. It took me about 10 minutes to create a profile for MySQL. I generated the script to create all the indexes for me and then ran it in MySQL, no problem. I have several applications that I ported from Access MDBs to MySQL, and I continue to use Access with them, thanks to MyODBC. I simply set up a DSN on my Windows box that points to the Linux box and the rest was a piece of cake. I dispute Nicholas's contention that a lot of Access queries will not work in MySQL. Technically, he is correct: if you try to run a query that says SELECT TOP 10 * FROM mytable, that of course won't work in MySQL; nor will Access's crosstab queries. However, if you leave them in Access and execute them against a MySQL database, almost all of them continue to work. There is an added advantage to this route, as well. Leaving them in Access preserves their existence as objects with names, meaning that you can create a couple of queries and use them in subsequent queries. This is a very powerful feature of Access, and there is no reason to abandon it when you move the data to MySQL -- unless of course you are also abandoning Access. If you have any specific questions, feel free to ask. Arthur > -------- Original Message -------- > From: "Nicholas Stuart" <[EMAIL PROTECTED]> > Subject: Re: MS Access and mySQL > To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> > > I have been there done that with old access data, but no forms. Your > plans should be focused around what you know and what your systems are > tied to. Since its an NT box you could go with pretty much any language > ie java/vb/c++. VB would be the obvious choice for ease of transfering > the Access VBA forms to straight VB. The only thing you have to be > careful is the access querys. A lot of them will not work on MySQL and > the funny thing is a lot of them will not work on M$'s on SQL server :) > go figure. > As far as the data goes the easist thing I found to transfer it into > mysql is a program called dbtools. You can find it at: > http://www.dbtools.com.br/EN/ It's fairly easy to use and has a great > import wizard. > If you have an specific questions let me know and I'll try my best to > answer them. > -Nick > > MySQL Newsgroup (@Basebeans.com) wrote: > > >Subject: MS Access and mySQL > >From: =?iso-8859-1?q?Jonathan=20Coleman?= <[EMAIL PROTECTED]> > > === > >Hi. > > > >I have a situation where a church I am doing some volunteer work for > >has a MS Access (office 97) database running on NT. They are (woohoo) > >upgrading to a QUBE (linux box) for a server which has mySQL installed > >(and I can upgrade it etc..) > > > >My job therefore is to > > > >a) port MS Access data and queries to mySQL database > > > >b) use the MS Access forms to access the data and queries through ODBC. > > > >Is there anyone who can point me in the right direction, either to > >where the searchable discussion archives are, OR even better, someone > >who has gone through this before? > > > >Cheers > >Jon > > > >http://digital.yahoo.com.au - Yahoo! Digital How To > >- Get the best out of your PC! > > > >--------------------------------------------------------------------- > >Before posting, please check: > > http://www.mysql.com/manual.php (the manual) > > http://lists.mysql.com/ (the list archive) > > > >To request this thread, e-mail <[EMAIL PROTECTED]> > >To unsubscribe, e-mail > <[EMAIL PROTECTED]> > >Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > > > > > >--------------------------------------------------------------------- > >Before posting, please check: > > http://www.mysql.com/manual.php (the manual) > > http://lists.mysql.com/ (the list archive) > > > >To request this thread, e-mail <[EMAIL PROTECTED]> > >To unsubscribe, e-mail > <[EMAIL PROTECTED]> > >Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > > > > > > > > > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
