weird issue with tables

[S.W.Eng]

HI everyone,

I made a table with some xyz coordinates and set the data format to decimal numbers, decimal, precision to 0.00.

All my numbers are correct except for the last number in the table that is -4.74, it displays correct in the table but when I pull up properties , in the content it shows  -4.740000000000001, I tried changing the precision but nothing changes.

Weird thing is that is I changes the number to -4.75, it displays correct and the content is correct.

This seems to happen only  when .74 is used.

I have tried changing the data format  but this keeps happening.

Is there something wrong here?

[pendean]

@S.W.Eng Why not use this to match the errant cell with an adjacent cell

or manually fix them in PROPERTIES

[h_s_walker · Accepted solution]

I've noticed that problem with some of my tables as well. I'm not sure why it does it, but the easiest way to sort it is to just change the format of the cell from decimal number to general. Admittedly you will have to type in the decimal places yourself, but you won't get the *.0000000000001 bit at the end 

[S.W.Eng]

I tried you suggestion unfortunately the match cell is greyed out when I select the errant cell and the one next to it, I also tried your second suggestion, and I can change alignment but when I try to change format  and additional format it just reverts back to varies on its own.

[S.W.Eng]

I tried your suggestions unfortunately when I highlight the errant cell with the one next to it, the match cell is greyed out, I also tried the second suggestion, it lets me change alignment but when I try to change format and additional format, no matter what I change it to it reverts back to VARIES on its own.

[S.W.Eng]

Thank you, that did work, I usually only use .00 so its not much extra work.

[catherine.watson]

Hi @S.W.Eng, I looked into this, and appears to be a known issue. Autodesk is putting the investigation on hold for now and a resolution has not been determined at this time. There might be some factors out of Autodesk’s control, or they may need more info to keep looking into it. For now, the workaround suggested above is also the best option we've found - thanks @h_s_walkerfor sharing the Accepted solution.