Number 1-20 field rounds to 2 decimal

[jim]

Project 2003: inserted a custom Number field to the task view. Example input
of 12.33456 is rounded to 2 decimal places (12.33). I can't seem to find any
information/discussion on this strange nuance. Thanks for any help in this
regard.

 

[JackD]

That is the way it is. If you want a different number of decimal places
displayed you will have to use a text field.
I typically avoid using number fields.

 

[jim]

Rounding for display is (maybe) understandable, I'm just surprised that the
number is actually rounded in the database. If you map a Number 1-20 field to
Access it's a double so it doesn't seem to be a variable type issue. Not sure
why Microsoft would go through the trouble to do this.

 

[John]

Rounding for display is (maybe) understandable, I'm just surprised that the
number is actually rounded in the database. If you map a Number 1-20 field to
Access it's a double so it doesn't seem to be a variable type issue. Not sure
why Microsoft would go through the trouble to do this.

Jim,
I don't know why MS designed Project that way but perhaps the spare
number fields were originally developed to hold additional cost type
data without the currency formatting.

Just a thought.
John

 

[Steve House [MVP]]

Have to admit I can't quite think of any quantities or measurements that one
encounters in project managment that have any practical need to be more
precise than 2 decimals though. Sure there are many things that need to be
very precise but they usually deal with engineering specifications, things
like that - not these rather gross quantities such as hours of work or tons
of coal or kilobucks of cost that business managment works with. I always
think back to my university days and remember what my professors would call
"empty precision." Sure you can carry a calculation to 6 or 8 decimal
places but most of the time what's the point?