Steve
Sun Jan 09 14:17:07 CST 2005
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?
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs
"John" <mjensen@theriver.com> wrote in message
news:mjensen-36EA8A.11414209012005@msnews.microsoft.com...
> In article <5B5AFF99-7DB0-4790-BD34-9CD7BFE58B19@microsoft.com>,
> jim <jim@discussions.microsoft.com> wrote:
>
>> 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