Toad World® Forums

Not a legal OleAut date

Has anyone else encountered the error message Not a legal OleAut date when using Quick Export -> Excel Instance -> Excel Instance… ? I’m exporting data retrieved from an Oracle dB.

I receive this message periodically and it cancels the export. In this latest example it read 249,937 rows and only exported 249,936. In total there were over 1 million rows.
However when I check the dates in the records around the last row exported all the dates are valid.

Is this some form of a conversion bug with dates between Oracle/Toad/Excel?

This is the full error log I receive. (I am using TDA 3.0.1.1734)

11:28:36 AM Thread (37) Export Started [4/13/2012 11:28:36 AM]
11:28:36 AM Thread (37) Export using connection: DB_NAME (USER), USER
11:28:36 AM Thread (37) Export using connection: DB_NAME (USER), USER
11:28:36 AM Thread (37) Export Wizard: Building object list
11:28:36 AM Thread (37) Exporting Data (1 of 1)
11:28:36 AM Thread (37) Object Table Result Set started.
11:28:43 AM Thread (37) Writing rows 0 - 1333309
11:30:33 AM Thread (37) Exception in WriteRows
11:30:33 AM Thread (37) Not a legal OleAut date.
11:30:33 AM Thread (37) Writing rows Finalize
11:30:34 AM Thread (37) Object Table Result Set finished with error: Not a legal OleAut date.
11:30:35 AM Thread (37) at Quest.Toad.ImportExport.Writers.WriterBase.WriteRows(FastTable fastTable)
at Quest.Toad.ImportExport.ExportObjectData.StartTableWrite(Object context)
at Quest.Toad.ImportExport.ExportObjectData.Begin(LogEventHandler logEventHandler, Dictionary`2 connections, Object context)
11:33:21 AM Thread (37) Export Finished [4/13/2012 11:33:21 AM]

Hi Tim,

I believe this is caused by an invalid date in your original data. Please see this thread below on Quest Support, if you haven’t tried this already.

https://support.quest.com/Search/SolutionDetail.aspx?ID=SOL67258

Can you please ensure that none of the dates you are trying to export are prior to January 1, 0100?

Thanks,
Mike Wilson
Quest Software

Thx!