In design view of the table for that field set the decimal places to 1 or as
needed.
Chris
> I have tried every option in table design view to show 1-2 decimal point
> values. Every time I enter a number like 2.6, it converts to 3.0. Can any
> one help me?
csheehan - 31 May 2005 06:39 GMT
> In design view of the table for that field set the decimal places to 1 or as
> needed.
[quoted text clipped - 6 lines]
> > values. Every time I enter a number like 2.6, it converts to 3.0. Can any
> > one help me?
Eric Blitzer - 31 May 2005 06:55 GMT
I find using Double for the filed size to be the best. Glad you solved your
problem.
Chris
> > In design view of the table for that field set the decimal places to 1 or as
> > needed.
[quoted text clipped - 6 lines]
> > > values. Every time I enter a number like 2.6, it converts to 3.0. Can any
> > > one help me?
>I have tried every option in table design view to show 1-2 decimal point
>values. Every time I enter a number like 2.6, it converts to 3.0. Can any
>one help me?
The default Number datatype is "Long Integer" - and an integer is, by
definition, a whole number.
If you want up to 14 decimal places precision, and complete values
from 10^-308 to 10^306 (or something of that order), use a Number
Double type. Unfortunately these numbers are *approximations*; some
numbers, for example 0.1, cannot be stored exactly and may cause
roundoff error at the 14th decimal place.
If you can live with exactly four, no more no fewer, decimal places
with NO roundoff error, use a Currency datatype.
The latest versions of Access have a Decimal datatype which lets you
explicitly set the number of digits and of decimal places, but I've
heard that there are bugs with it (it may not sort correctly for
example).
John W. Vinson[MVP]