Bug #75450 "Exception from HRESULT: 0x800A03EC" related to old date
Submitted: 8 Jan 2015 16:48 Modified: 26 Feb 2015 0:42
Reporter: Tomas Aarvak Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL for Windows: MySQL for Excel Severity:S2 (Serious)
Version:6.2.4 OS:Microsoft Windows (Microsoft Windows 8.1 Pro)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[8 Jan 2015 16:48] Tomas Aarvak
Description:
Hi, after installing Workbench 6.2 and MySQL for Excel 1.3.3 on a Win8.1 pc with Office 2013 (MSO15.0.4675) I got problems with editing data through Excel and got error message "Exception from HRESULT: 0x800A03EC" when importing data for editing. After a lot of testing I found out that this is related to columns formatted (in the SQL-database) as DATE, containing dates older than 1900! So, a date like 1889-02-27 would create this error message and make it impossible to edit the table. This is a problem not seen on a pc with Win7 and Office 2011.

How to repeat:
Removing data with date older than 1900-01-01 would make the editing in "mySQL for Excel" work.
[10 Jan 2015 20:27] MySQL Verification Team
Error

Attachment: excel_date_issue.png (image/png, text), 41.56 KiB.

[10 Jan 2015 20:28] MySQL Verification Team
Thank you for the bug report.
[13 Feb 2015 17:39] Javier TreviƱo
Posted by developer:
 
Fixed the import of MySQL data into an Excel range to convert any dates before the Excel minimum date (January 1, 1900) to text so Excel does not throw a COM Exception.
Verified that these dates can be changed on Edit Data operations and saved back to MySQL without any errors.
[25 Feb 2015 20:11] Philip Olson
Posted by developer:
 
Fixed as of the upcoming MySQL for Excel 1.3.4  release, and here's the changelog entry:

An error similar to "Exception from HRESULT: 0x800A03EC" was generated
when importing data with dates older than January 1, 1900. Dates older
than this are now converted to text, as to prevent the COM exception.

Thank you for the bug report.