Apache OpenOffice (AOO) Bugzilla – Issue 61949
Date values shifted by 2 days on table import via copy & paste
Last modified: 2006-08-01 12:59:58 UTC
When a table is mported via drag and drop, date values are shifted by 2 days in OOo. To reproduce: - open attached .mdb file with Access - create a new OOo database (or use the attached example) - drag table "Test_Date" from Access to OOo's tables area - check create primary key in the copy table wizard - import all colums - set field type for column Datum to Date - open the imported table and set display format for column Datum do date -> Colums Datum and Text show different values but should sho the same. Bug found in 2.0.1 and verified in m156
Created attachment 34088 [details] sample mdb file
Created attachment 34089 [details] resulting .odb file
Also the Import from Calc is broken. It's a severe defect.
> Also ... http://qa.openoffice.org/issue_handling/basic_rules.html#one_per_issue
I have made 62797 for copy&paste from Calc. But I still think, that the comment here is right. When I copy from Access97 the clipboard format is RTF. I therefore tried other sources of rtf. So I found the rtf-clipboard form of Calc leads to +2 days but also the rtf-clipboard format from WordPad leads to +2 days and copy&paste from WordViewer too. So my comment is, that it is not a problem of Access but of pasting from clipboard in rtf-format.
This problem has also been reported by a French user on the n-l dev list. It sounds like the eternal "wrong reference date implementation" issue used by Calc and Writer which is not the accepted "database reference date". Can this not be fixed once and for all, this problem has been plaquing OOo for as long as I can remember (i.e. since the code was first released) ? I seem to recall that the problem had also occurred in StarOffice 5.2 at one stage, so it really isn't new. See also issues 8801, 22687, 22688, 34666, 24313, and 23878 as examples of the continuing recurrence of the problem, which at the time was allegedly fixed. Like a bad dream, it keeps coming back to haunt us, and in terms of product quality, is very detrimental to all who rely on reliable date calculation. Alex
clu->oj: your turn
set target
oj->clu: Could you please test this one in a current release m174 e.g. I couldn't reproduce it there.
I see the same issue using OO 2.0.2 with either HSQLDB or Postgres 8.1.4 when copying from Calc.
clu->oj: still repro in a 680m176
Isn't repro in a m179 and even msc couldn't repro it in a m176. So I set this one as duplicate to 62797 *** This issue has been marked as a duplicate of 62797 ***
.