Bug #10751 | Access Conversion appears to succeed, but fails | ||
---|---|---|---|
Submitted: | 19 May 2005 19:00 | Modified: | 20 Jun 2005 17:36 |
Reporter: | Dave Bennett | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Migration Toolkit | Severity: | S1 (Critical) |
Version: | 1.0.6beta | OS: | Windows (Win XP) |
Assigned to: | CPU Architecture: | Any |
[19 May 2005 19:00]
Dave Bennett
[20 May 2005 13:34]
Richard Black
I've also seen this behaviour, but not consistently
[20 May 2005 17:36]
MySQL Verification Team
Could you please describe or attach a small mdb file that it failed for you, because I was able for to migrate the Access db.
[13 Jun 2005 18:49]
Beat Arnet
Version 1.0.7 Beta MS-Access 2002 Database in format 2000 Some tables worked fine, two led to errors which were only visible in the "Advance tab": Creating table Document ... CREATE TABLE `RadBase`.`Document` ( `DocID` INTEGER(10) NOT NULL AUTO_INCREMENT, `PatID` VARCHAR(50) NULL, `PID` INTEGER(10) NULL, `DocType` VARCHAR(100) NULL, `DateType` VARCHAR(1) NULL, `DocDate` DATETIME NULL, `ArchiveDate` DATETIME NULL, `Author` VARCHAR(100) NULL, `FileSpace` DOUBLE(15, 5) NULL, `NumDocs` INTEGER(10) NULL, `PathDoc` VARCHAR(255) NULL, PRIMARY KEY (`DocID`), UNIQUE INDEX `PathDoc` (`PathDoc`), INDEX `{6AA6C425-45E5-4865-BD7D-C1F1429AF556}` (`PID`), INDEX `PatID` (`PatID`), INDEX `PID` (`PID`), INDEX `StudyDate` (`DocDate`) ) ENGINE = INNODB; An error occured while executing the SQL statement. Incorrect index name '' Nothing was reported at the end of the migration process but two tables were missing. Repair and compact did not help nor setting up a new database and importing all tables and relations. Tried to change the name for the index INDEX `{6AA6C425-45E5-4865-BD7D-C1F1429AF556}` but could not see where to do that within MS-Access because the name was not seen. Migrating to MS-Access version 2002 did not help nor did editing the SQLCreate.sql (the file which is produced first). Could not solve the problem...
[20 Jun 2005 23:00]
Bugs System
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".