RE: MS Access to MySQL - Database Conversion
| From: | Bob Horton | Date: | Wed, 05 Jul 2000 14:51:36 +0000 |
| Subject: | RE: MS Access to MySQL - Database Conversion | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-4961@lists.php.net to get a copy of this message | ||
You can find a simple little script that you put in as a module in Access
that will dump everything in raw SQL go to:
http://www.cynergi.net/exportsql/ ). When you have
created the database in
MySQL then you do a
mysql [-umyuser] [-p] mydatabase < esql_add.txt
and it will populate MySQL with all of the information from Access.
Completely trivial!
Converting the code will be a little more work but shouldn't kill you.
Otherwise (and I haven't tried it, I'm just thinking out loud) you could
consider a FAT partition on the MySQL machine and still using an ODBC driver
... but even as I say that I'm not sure if it will actually work or not.
> -----Original Message-----
> From: Tom Peck [mailto:tompeck@paradise.net.nz]
> Sent: Tuesday, July 04, 2000 9:30 PM
> To: php-general@lists.php.net
> Subject: MS Access to MySQL - Database Conversion
>
>
> Hello everyone
>
> I have a site which uses a Microsoft Access database, connected
> through ODBC. This is currently hosted on a Windows NT Machine,
> without problems. Now it needs to be ported to a Linux machine -
> and a MySQL database.
>
> My Question:
>
> What is the easiest way to convert the data from one database to
> the next? Secondly - I haven't dealt with MySQL before - how
> much of the code will need to be changed for it to work with the
> MySQL database?
>
> If there's too much work involved, I may stick with the Access
> database. How can this be setup on the linux machine? It it was
> possible - would the code need to be changed?
>
> Thanks everyone - I look forward to your reply's.
>
> Tom Peck
>