Decimal, precision

[scubadiver]

"The decimal field's precision is too small to accept the numeric you
attempted to add".

The problem field has a currency format (£00.00)

Precision -> 4
Scale -> 4
Decimal places -> 2

This particular field is a calculated value and is taken from a query where
the property has two decimal places.

Any ideas?

 

[Allen Browne]

If this is a linked table, it might be this problem:
http://support.microsoft.com/kb/270704/en-us

Decimal fields are not really usable in Access. Even really basic things
like sorting them fails:
http://allenbrowne.com/bug-08.html

 

[scubadiver]

Hi Allen,

thanks for the info.

The really strange thing is that the field I use to calculate the total fee
is virtually the same but when I click on the field, I don't get the error.

David

 

[scubadiver]

The other message I get is "too many fields defined".

Does this mean I have gone over 255 fields. I have less than 100 so I can't
see how.

 

[Duane Hookom]

If you have added and deleted and changed fields within a table you may
reach the limit long before 255. Compacting your database may fix this for
you.

HOWEVER, if you do a little scanning through this news group you will see
that most experienced Access developers will rarely have more than about 30
fields in a single table. More than that generally suggests your tables are
not normalized. Since we don't know what kind of information you are storing
in what types of fields, we can't tell for sure.

 

[scubadiver]

I have tried compacting the database but it doesn't work so I am going to
start again.

Look at the post directly above this one: "reducing the number of fields
required"?

Give you some info.

David

 

[mnature]

This particular field is a calculated value and is taken from a query where

the property has two decimal places.

You have placed a calculated value in a field?

You should never, ever, put a calculated value into a field. There are
numerous important reasons for this rule. Bottom line is: only put
calculated values into forms and reports. By definition, a calculated value
can change. If you have placed that value into a field you are defeating a
valuable property of your database, which is to give you the most up-to-date
information based upon your data.

If the calculated value is a static number, one that is not subject to
change, then it is very feasible to calculate the number outside of Access,
and then import it in a final form into your table as a fixed number.