Bug #70925 Importing tables with GUID to excel - exception
Submitted: 15 Nov 2013 17:50 Modified: 21 Mar 2014 5:16
Reporter: Konstantin Balyshev Email Updates:
Status: Closed Impact on me:
Category:MySQL for Windows: MySQL for Excel Severity:S3 (Non-critical)
Version:1.1.3 OS:Microsoft Windows (x64)
Assigned to:
Tags: Excel2013, Guid
Triage: Needs Triage: D2 (Serious)

[15 Nov 2013 17:50] Konstantin Balyshev
Hi! Whenever I try to import a table with GUID into Excel 2013 with MySQL for Excel I get an error "Exception from HRESULT: 0x800A03EC". This happens only if I export a table with char(36) field. If I change definition to char(37) or varchar(36) it starts working ok as long as Excel stops treating the field as GUID.  

How to repeat:
Create the table for import ant try to import with MySQL for Excel 1.1.3 in Excel 2013.

create table tags_dir(
TagID char(36) primary key,
Tag char(20),
TagType char(1),
Description varchar(255)

insert tags_dir
select UUID(), "EMAIL", "M", "Manager's e-mail";
[16 Nov 2013 0:00] Miguel Solorzano

Attachment: 00_Excel_Error.png (image/png, text), 169.18 KiB.

[16 Nov 2013 0:06] Miguel Solorzano
Thank you for the bug report. Verified as described with Excel 2010.
[4 Feb 2014 19:15] Javier Rivera Zavala
Posted by developer:
Guid data from the given example, is now imported correctly.
[11 Mar 2014 21:50] Javier Rivera Zavala
Posted by developer:
The Creation of named tables required a few more parameters to work fine in all cases.
[19 Mar 2014 3:36] Philip Olson
Pending QA Review:

Fixed as of the upcoming MySQL for Excel 1.2.1 release, and here's the changelog entry:

The creation of named tables did not function in all cases during an
import, and could generate an exception.

Thank you for the bug report.
[21 Mar 2014 0:57] shawn holt
Is there a patch available for this?
[21 Mar 2014 0:58] shawn holt
OR a development release?
[21 Mar 2014 5:16] Philip Olson
Shawn, there isn't a patch or developmental release available, but the stable release is pending.