MySQL Bugs: #31313: Migration Toolkit ignores OLE objects in MS Access

Bug #31313	Migration Toolkit ignores OLE objects in MS Access
Submitted:	1 Oct 2007 12:18	Modified:	20 Oct 2009 5:55
Reporter:	Bogdan Degtyariov	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S4 (Feature request)
Version:	1.1.12	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	access, Migration Toolkit, OLE

Description:
When trying to import OLE data from MS Access tables in MySQL database migration toolkit ignores the contents of OLE object columns. It just creates empty LONGBLOB columns with names that correspond to the ones from MS Access.

How to repeat:
1. Create a new table in MS Access with at least one OLE object
2. Insert a new record in this table. OLE column should not be empty, so put anything there (say picture)
3. Run the Migration Toolkit and choose .mdb file as the source and MySQL as the target
4. Select the Access table for migration etc
5. Migration Toolkit reports about the successful completion.
6. See an empty LONGBLOB field in mysql target table. All other fields such as int/varchar/datetime are imported correctly.

Hi,

this is a know limitation of the MS Access JDBC/ODBC bridge and we can do nothing to fix this issue within the current implementation.

The fix would have to be implemented on the MS Access side or in the bridge (and this is not likely to happen).

Sorry about that,
Mike

Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Migration Tool into MySQL Workbench. We won't add this feature request anymore.

More informations about MySQL Workbench you will find here:

http://dev.mysql.com/workbench/