Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Lost Format of Integer (and Other Numeric Fields) | ||||||
---|---|---|---|---|---|---|---|
Product: | Base | Reporter: | rk601 <rk601> | ||||
Component: | code | Assignee: | AOO issues mailing list <issues> | ||||
Status: | UNCONFIRMED --- | QA Contact: | |||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | drewjensen.inbox, issues | ||||
Version: | OOO310m4 | ||||||
Target Milestone: | --- | ||||||
Hardware: | Unknown | ||||||
OS: | All | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
rk601
2009-03-06 16:14:55 UTC
*** Issue 99981 has been marked as a duplicate of this issue. *** Please note that issue #99981 is NOT a duplicate of this issue #99980. Created attachment 63894 [details]
example database
Confirmed w/ OOO310m_17 and OO.o3.1, Ubuntu 9.04 NOTE - I'm leaving the actual issue as unconfirmed - not because this doesn't happen but because it appears there are a couple of problems all working together. This perhaps should be broken into multiple issues and perhaps an RFE. 1) User defined formats - these seem to be changed after the file is saved and reopened. So "ABC"0000 after re-open becomes "ABC"# under m_17. Under 3.1 it came back as "ABC""/"# (Also I kind of recall seeing an Issue about this with regards or something similar, under Calc or Framework...will need to do some searching) 2) Form controls. Individual controls seem to pick this formatting up and use it. Controls in table Grid columns do not - unless they are used as part of a Master/Detail form, and the Master form is using an individual control properly formatted. (~clear as mud..sorry) 3) Three times while testing this with a form using stand alone controls the DBEngine throw an error saying that a duplicate value was rejected for the Auto_Increment field. Closing the form and repoening it put all back right...there did not seem to be a pattern to when it would do this however. (Note there is an unconfirmed Issue in the system right reporting just this behavior that has nothing to do with formats - so need to see if I can duplicate this without the format being involved) 4) Query designer - the default format is honored when the you first create a query. After closing and the exectuting the query later it is lost. (Again I think there might be an existing issue on this...more searching) 5) When creating a form the controls that do honor the formatting seem to pick this up at design time and then save it - so that if you later change the format for field definition and run the form you still get the old formatting. (This might be the RFE) @rk601 - I think it would be best if you could help me work through this and we discuss it on one of the mailing lists first and then come back to the issue tracking system. users@dba.openoffice.org seems like a good list. Additional information regarding formatting errors in FormattedField controls. 1) in a GridControl - a FormattedField >does< pick-up and retain the formatting; (eg, format=(1234.00) does display with two decimal places (as in a Currency field) 2) an individual formatted field control - not bound to a data item - does not retain formatting. Both decimal and currency formats display as integers. [the formatted field is filled in with computed results from a SELECT SUM(... ) stmt.] ooo310_m19/winXP |