By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,474 Members | 1,273 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,474 IT Pros & Developers. It's quick & easy.

bug in MS Access/XP Pro

P: n/a

I have found what looks like a bug in Access or XP Pro.

When I have the following in a table in Access

1996 0.08715292
1996 12.98775
1996 1.987653
1996 0.09476294
1996 0.1012828
1996 1.25012E-06
1996 0.08638828
1996 0.09060681
1996 0.09808088
2010 128.9784
2020 1.568336E-05

and I save the table as a CSV file...I get the following


the order is different, that is not a bug, just microsoft's stupid

The problem is that some numbers in the second column have been
truncated. A closer look shows that numbers of the form a.b have been
truncated to 2 decimal places (as is set in the regional settings),
but numbers of the form a.bexp-c haven't. I don't know if there is
logic behind this or not. But...

a) I wouldn't expect Access to truncate ANY numbers when writing to a
csv file REGARDLESS of the regional settings for number
representation. To do so is dangerous and makes Access behave
differently on different machines.

b) IF it decides to truncate numbers on writing, I would expect it to
round the numbers off, rather than just truncate. Otherwise the
answer is not just less accurate, but ABSOLUTELY WRONG.

c) IF it decides to truncate numbers to 2 decimal places, I would
expect it to truncate ALL numbers, so as to minimise confusion.

Does anyone have any comments? I don't know whether this is really a
bug or there is some Microsoft logic behind it. If it is a bug, it
makes me very untrusting of MS Access generally.

Nov 13 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.