https://issues.apache.org/ooo/show_bug.cgi?id=119938
Randy Wester <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Randy Wester <[email protected]> --- I have also run into this same problem in this situation: - Running latest available version as of 2012-NOV-23: - Accessed an external database application's tables using an ODBC connection. Some data tables will open, some will not. (The application is Sage Quantum 2013, formerly known as the Canadian version of Simply Accounting, which uses MySQL as a back-end application.) - The data tables that will not open contain a date field that appears to contain invalid data when evaluated as a date. Other things observed: - The date field evaluates as 1-Jan-1901 in Microsoft Access, which won't allow editing of the particular record (error message is that the data has changed). Once the date field has been edited in OpenOffice.org, the record can be edited. The date field evaluates as 03/01/1 00:00 in Open Office 3.2, which _will_ allow editing of the date. The actual data in the date field may be a flag (such as '-1') used by the application program to indicate a null value, or may be an actual null value. ( I can't tell, my MySQL database powers are limited ) The error message _only_ appears when attempting to open tables that have these date fields in them. Other tables containing dates, in the same database will open successfully. This issue does _not_ appear in this situation: Same situation, except running an older version of Open Office: Running OpenOffice.Org v. 3.2.9502, -- You are receiving this mail because: You are on the CC list for the bug.
