Problem with decimal places in Access 2003

[Avery]

For some reason my Access 2003 will automatically round any number to the nearest interger. I have tried it on two different computers with the same result. Is this a known bug with a fix? I can't seem to find any info on it.

 

[Lynn Trapp]

What is the in the Field Size section for the Numeric field when you view
the table in design view?

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Security FAQ: http://support.microsoft.com/support/access/content/secfaq.asp

For some reason my Access 2003 will automatically round any number to the

nearest interger. I have tried it on two different computers with the same
result. Is this a known bug with a fix? I can't seem to find any info on it.

 

[John Vinson]

For some reason my Access 2003 will automatically round any number to the nearest interger. I have tried it on two different computers with the same result. Is this a known bug with a fix? I can't seem to find any info on it.

This usually means that you have created a field using the default
Number datatype: Long Integer. An Integer, by definition, has no
decimal places.

If the field contains money, or if you can live with exactly four (no
more, no fewer) decimal places use a Currency datatype instead of
Number. If you need more decimal places use Float (for seven) or
Double (fourteen), but be aware that both of these datatypes are
approximations and that you will have "round off error" - for
instance, storing 0.1 will actually store something like
0.0999999999999983, so comparing a Double to a Double might not find
the data you expect.