Issue 56871 - In base, Forms, TableControl does not format numbers correctly
Summary: In base, Forms, TableControl does not format numbers correctly
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO 2.0 Beta2
Hardware: PC All
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2005-10-28 14:34 UTC by b0b15950
Modified: 2017-05-20 10:47 UTC (History)
2 users (show)

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

Simple Base Database titled "IssuesLog.odb" (24.18 KB, application/vnd.sun.xml.base)
2005-10-28 14:37 UTC, b0b15950
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description b0b15950 2005-10-28 14:34:29 UTC
Using 2.0.0 Final, xp pro SP2 fully updated, dual P3 processors, 768Mb memory

In Base, Forms; create new form and and TableControl in blank form using a table
containing integers as the control source. 

Not that integers are displayed as two decimal place (2d.p.) numbers.

Example attached.

In Base, Forms;Open TableControlTaskForm
Note the 2 d.p. numbers in fields TaskID, %done, IssueID and Priority.

Close form

Open TaskTable and note the above fields are all integer.

There are other issues that mention defect formatting in tables and this problem
may be linked. Other issues tend to involve external data sources. The issue
reported here is generated entirely within Base. It is given priority P2 because
it effectively stops table format sub forms from being generated properly.

There is a work around. Hide columns that are defectively displayed and add new
columns containing the same fields. Format the new columns as integer. This
action also generates unexpected and inconsistent, intermittent behaviour,
including on one occasion a complete crash of O2.

Can somebody tell me if I need to repeat automatically generated crash reports
as issues in the qa project please? I have experienced 6 crashes, all reported
through the automatic reporting service but have not replicated them in qa issues.
Comment 1 b0b15950 2005-10-28 14:37:12 UTC
Created attachment 30959 [details]
Simple Base Database titled "IssuesLog.odb"
Comment 2 b0b15950 2005-10-28 14:58:08 UTC
Summary should read "... TableControl does NOT format numbers correctly"
Comment 3 marc.neumann 2006-02-08 10:57:07 UTC

I can reproduce this. The Table Grid wizard doesn't respect the type of the
database field. f.e. add 2 decimal places for an integer field.

as a workaround you can change the format of the field by right click on the
field in the design view and then choos "control..." . In the property browser
you can change the decimal places.

Anyway a reassign it to the right developer for fixinf the table grid wizard.

Bye Marc
Comment 4 b0b15950 2006-10-05 10:29:37 UTC
Confirmed and reassigning issue.
Comment 5 b0b15950 2006-10-05 11:41:38 UTC
Why can't I change the status of this?
Comment 6 Frank Schönheit 2006-10-05 12:18:39 UTC
probably because you lack permissions. What are you trying to do? Why did you
move the issue back to dbaneedsconfirm?
Comment 7 b0b15950 2006-10-05 14:42:12 UTC
Hi fs, I didn't move it back to bdaneedsconfirm, the system did. I have been 
trying to move this issue forward for some time and it always seems to have 
the 'unconfirmed' status when I look at it (I now see it is set to NEW). I 
want to contribute to OOo but the issues handling system doesn’t let me. I 
can't be the only volunteer that gets charred off with it, (so stops helping).

Base is probably the worst application within OOo for usability and I would 
like to contribute to moving it forward.

Anything you can do to get issues handling working would be great. In 
particular the ability to change the unconfirmed status when the history 
clearly shows that another user has replicated the problem.

Best regards
Comment 8 Frank Schönheit 2006-10-05 20:00:53 UTC
This issue has been confirmed on 2006-02-08 - nearly 8 months ago -, as you can
see at It is
assigned to me, and targeted for "OOo Later" (which unfortunately means it
hasn't a too high probability to be fixed in a timely manner).

For contributing, in particular for how to get privileges to confirm issues, see
Comment 9 b0b15950 2006-10-05 20:55:10 UTC
Thanks for getting it moving fs, I appreciate it. Apologies for pressing any 
wrong buttons.
Best Regards
Comment 10 b0b15950 2006-10-05 21:16:20 UTC
Thanks for getting it moving fs, I appreciate it. Apologies for pressing any 
wrong buttons.
Best Regards
Comment 11 Marcus 2017-05-20 10:47:51 UTC
Reset assigne to the default "".