MySQL Bugs: #21734: Migration Tool Does not Convert Access Autonumber Fields

Bug #21734	Migration Tool Does not Convert Access Autonumber Fields
Submitted:	19 Aug 2006 16:48	Modified:	28 Sep 2006 22:17
Reporter:	[ name withheld ]	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S3 (Non-critical)
Version:	1.1.2 Beta	OS:	Windows (Windows XP)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Autonumber fields in Access databases are converted to number fields after using the Migration tool. The autonumber fields in the MDB file were both autonumber and a primary key, but only the autonumber was not converted correctly.

How to repeat:
I am using an Access Database newly created in Access 2002 (10.2616.3501) SP1. In Access, I started with a "blank database" and created a table in design view with an autonumber field and a text field. One thing to note is that even though I am using Access 2002, Access created an Access 2000 database - at least thats what it shows in the title bar in Access. 

I then used the Migration Tool to convert this file to MySQL. After selecting the path to the database, I basically clicked next all the way through the wizard - all default settings were used. 

I created an ODBC data source to open the database from Access and the autonumber field has been changed to a number field. Since the autonumber field was also the primary key, I have several SQL statements that depend on the ID field to be incrimented automatically. 

Suggested fix:
There seems to be a bug in the migration tool somewhere but I have no idea how to fix it.

Thank you for the bug report. I was unable to repeat with the new tool
MySQL Migration Toolkit, please download it and try again:

http://dev.mysql.com/downloads/gui-tools/5.0.html

Thanks in advance.

Is it possible that something besides the migration tool is causing the problem? I was thinking that there are several DLLs that are common for database access such as ADO, DAO, etc. There could also be common Access DLLs mixed into the migration process somehow. Does the migration tool depend on ADO get the database schema? Maybe there is a bug in thse common DLLs? If its possible, can you suggest some possilities and I will post the version numbers that I'm using. I am a developer too so there could be several versions of ADO on my PC and some could be very dated.

I will try the migration tool in the bundle tonight. I originally downloaded the single install for just the migration tool.

Thanks.

Thank you for the feedback. I don't think that is the problem instead a
bug fixed how you can see bug:

http://bugs.mysql.com/bug.php?id=10823

Please test version 1.1.1 Beta.

Thanks in advance.

Thank you for the feedback. Which is your Java runtime version?

Could you try to start the Migration Toolkit from the command line testing the following paramter:

MySQLMigrationTool.exe -Xmx 256m
MySQLMigrationTool.exe -Xmx 384m
MySQLMigrationTool.exe -Xmx 512m

also

MySQLMigrationTool.exe -debug

The problem is not that Java is not found but that initializing the JVM returns an error.

Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".