It is my understanding that Access only handles
currency to four decimal point accuracy.

Is this true, and is there an easy workaround if it is.
It is turning into a minor problem lately as it seems like
more and more people are going to five places.

tom wrote:
> It is my understanding that Access only handles
> currency to four decimal point accuracy.
>
> Is this true, and is there an easy workaround if it is.
> It is turning into a minor problem lately as it seems like
> more and more people are going to five places.

Don't use currency data type. :-)

--
Joseph Meehan

Dia 's Muire duit

tom wrote:

> It is my understanding that Access only handles
> currency to four decimal point accuracy.
>
> Is this true, and is there an easy workaround if it is.
> It is turning into a minor problem lately as it seems like
> more and more people are going to five places.

Use DECIMAL(20, 5), or DECIMAL(21, 6) employing the extra decimal place
to implement a custom rounding alorithm (the DECIMAL type exhibits
symmetric truncation by nature).

Like the CURRENCY type, DECIMAL is fixed point, called an 'exact
numeric type' in the SQL-92 standard, but without the inherent rounding
rules, etc.

For monetary data do not, repeat, do not use floating point (Single and
Double), described as 'approximate numeric types' the the SQL standard.

Jamie.

--