Date: Sat, 20 Jul 2002 12:52:00 +1000 (EST)
From: Neale Banks (
Subject: Re: Moving Data from M$ Access to My SQL

On Fri, 19 Jul 2002 wrote:

> We are looking at getting out of the Microsoft vyse, but have done a
> lot of work on a Database in Access 97. What sort of process needs to
> be pursued to move that data into My SQL. Can the data be readily
> exported or does it all need to be re-entered. Any pitfalls to watch
> out for?

Have a look at exportSQL at:

"exportSQL is a Microsoft Access module which exports Access Database into
MySQL, mSQL and PostgreSQL."


Date: Thu, 06 Feb 2003 09:25:25 +1100
From: Donovan Craig (
Subject: Re: MySQL talk, what would you like to hear?
Organization: Snapfrozen Solutions
X-Mailer: Sylpheed version 0.8.6claws123 (GTK+ 1.2.10; i386-debian-linux-gnu)

Hi Andrew,

In the contributed section of the mysql site, there are a heap of tools
for that sort of thing.




Date: Mon, 10 Feb 2003 14:45:55 +0200
From: "Ulas B. Baloglu" (
Subject: Re: port 3306 help

I am using or will use (if i can connect) mysql-front or
Access2MySQL_v11 to make the conversion.

Date: Mon, 10 Feb 2003 14:08:06 +0100
From: Mathieu Laurent (
Organization: Qwentès S.A.
Subject: Re: port 3306 help

Ms Access to mysql



From: "Justin MacCarthy" (
Subject: RE: [ILUG] starting with MySQL server ?
Date: Thu, 4 Jul 2002 13:17:27 +0100

> Hi Folks,
> I have an access2000 database with only one table whihc I would
> like to move to an odbc setup with a mysql server on a linux box,
> and keep the access client on the winME desktop.
> I have spent the morning googling for faq's or howto's but I
> havent found anything suitable.. Mabye just not simple enough for me

Step 1:

Step 2: install ODBC mysql drivers onto the WIN box

Step 3:
Connect your Access front end to the SQL datasource

Hope that helps.


From: Marcus Furlong (
Date: Tue, 23 May 2006 21:04:30 +0100
Subject: [ILUG] Re: Locked M$ DB

Sonic wrote:

> Does anyone know how to unlock a M$ access db file. My mate has
> managed to forget the password (or set it wrongly as he put it) for a
> database which contains all his other passwords. I don't really use
> access so all I can tell you is that when I try to open it I get a
> message saying I don't have permission to open it.

I remember using the following script a good while ago and it worked then, but I remember it didn't work on the newest Office files:

Another option is to overwrite the workgroup file (contains all valid users etc). Create a new database with new users (similar usernames and groups if possible), then find the workgroup file (.mdw I think) and overwrite the original. I've got the feeling I may have left out some step along the way, sorry but it's been a while, anyway some variation of the above worked for me too.

P.S. When you do get it done, the next step is to run convert-Access-to-MySQL script: