I have an append query that appends records to a new table. But for some reason it is rounding the figures of my numbers and I have no idea why.
I'm sure there is a really simple explanation but any help would be great.
Thanks so much
I have an append query that appends records to a new table. But for some reason it is rounding the figures of my numbers and I have no idea why.
I'm sure there is a really simple explanation but any help would be great.
Thanks so much
To what precision is it rounding? What is the data type of the field in the destination table?
A couple of things to look for:
Are you sure it is actually rounding the numbers, or is it just a display (format) issue? Are they rounded if you open the table itself?
Is the rounding to the nearest integer, i.e. before the decimal point? If so, check the data type of the table field that is giving you the problem - if it is number - integer, that is the problem - it needs to be number - single (or number - double)
John
Hi yeah I though that but the data type is number. And in the table shows the rounded finger. I cant understand it. Even when I enter in a new number in my form it rounds it for some reason.
I cant think why it is doing it.
What is the field size?
Long Integer. It goes into a union query first and then an update query moves it to the table. I cant understand it though because if I look in the union query the amounts have decimals. So somewhere in the update or the actual table is rounding the numbers.
Your problem is the "Long Integer" field size. Integers do not have a decimal portion. If you want to keep the decimal portion, you have to use Single" or "Double" as the field size.
The query will show the decimals because it is a calculated field. The decimals are lost and the values rounded when the data is appended to the table. Changing the field size to single or double should resolve your problem.
John
I'd also consider Currency, which will avoid the potential floating point issues that Single and Double can have.
Sweet thanks so much. That solves that. What floating point issues can arise pbaldy?
2+2 might not equal 4. It might be 4.00000001.