Larry, This is not really a bug, this is a limitation of a data type that uses only 4 bytes to store the value. You cannot preserve precision to more than 6 significant digits with the REAL data type. Counting the "." as a significant digit, you are asking for 7.
Bill You must convert this datatype to DOUBLE, and then round the DOUBLE values to the nearest tenth. On Thu, Nov 18, 2010 at 9:18 AM, Lawrence Lustig <[email protected]>wrote: > A client started experiencing a big problem with REAL numbers after the > last update to 7.6 Windows. > > Their database is full of values such as 50000.1 (which represent a > customer and a location). Previously, there was no problem. > > Starting this morning, if they do SELECT CustNo FROM Customer, there's no > problem, the number appears as 50000.1. However if they do BROWSE CustNo > FROM Customer, or use any form that shows CustNo, the value appears > as 50000.099999999999. > > This only occurs when there are five or more digits to the left of the > decimal place. I can reproduce it in RRBWY14 with the following code: > > UPDATE Levels SET LevPerc = 50000.1 WHERE LIMIT = 1 > BROWSE LevPerc FROM Levels > > My question is, is there any setting that governs these formatting issues > that I can change to get the customer back to "normal"? I can't find > anything pertaining to FLOATs except SET TOLERANCE, which doesn't do the > trick. > -- > Larry >
