Issue 62245 - Calc field formats not correctly overtaken by import in data source
Summary: Calc field formats not correctly overtaken by import in data source
Status: UNCONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.1
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-18 17:50 UTC by msftrncs
Modified: 2013-02-07 22:42 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description msftrncs 2006-02-18 17:50:50 UTC 
I imported from Calc a table of data that included a time formatted column, 
which contains just a length of time.  This column formatted just fine in 
Calc, 36 hours formatted as 36:xx.  When in a Base table, numerically the 
value was represented as 1.5xxx but when I selected to format the column as 
[H]:MM, all my times where MODulus at 24 hours (12:xx for the 36 hour 
example).  I switched back to a numeric formatting and the numbers returned to 
1.5xxx (in the case of 36:xx hours).

I tried importing this field as a [TIME] field and that resulting in the same 
thing.  Almost seemed like Base didn't accept greater than 24 hours in a time 
format?
Comment 1 christoph.lukasiak 2006-02-20 11:58:29 UTC 
clu->protocol: this is one of many cases we have this problem (field formats of
calc and database differ in many cases) - i remember there exist some bugs in
this direction, but i cannot find one that would really fix, so i want to take
this one as 'master' for this problem
Comment 2 Unknown 2010-11-12 10:23:32 UTC 
Created attachment 74692