Issue 70618 - Calc-DB import date not correct
Summary: Calc-DB import date not correct
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: christoph.lukasiak
QA Contact: issues@dba
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2006-10-19 20:51 UTC by agdconsulting
Modified: 2013-08-07 15:45 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description agdconsulting 2006-10-19 20:51:07 UTC
Imported a spreadsheet into a DB table (by drag-n-drop from Calc to Base
window).  The "Copy Table" dialog comes up and proceed to import the table with
a "Create Primary Key" enabled.  The date in "time" column is imported
incorrectly - in spreadsheet is "06/01/06" (June 1st, 2006) but in base is
"06/03/06" (June 3rd, 2006).

Tried on Linux (2.0.2) and Windows (2.0) and MySQL and OO_Base formats.  Appears
in all cases.
Comment 1 christoph.lukasiak 2006-10-23 11:39:08 UTC
clu->agdconsulting: works fine for me in general, like described - may you
attach a sample spreadsheet (is it anyway formatted?) and describe what you
choose in the copy table wizard, because anything must be different even if the
description seems to be precise

thx
Comment 2 christoph.lukasiak 2006-10-24 15:59:13 UTC
may you also add your language settings (office and operating system) 

thx
Comment 3 Regina Henschel 2006-10-24 23:05:52 UTC
Please use the newest version of OOo, the former bug (issue 62797) of two days
offset is fixed now.
Comment 4 christoph.lukasiak 2006-11-20 11:08:44 UTC
no repro, no respond
Comment 5 christoph.lukasiak 2006-11-20 11:13:52 UTC
=> close - do not hestitate to reopen this issue if still occurs in a current
version and you have to add further hints for better reproducebility