I can't resist chiming in even though I'm probably way out of my league. If I understand you, the custno is a sort of combo field that includes an id # plus a ".1" which identifies a location? If that's correct, then they're using the "tens" decimal value to represent a location? Seems way far out and wrong way to do that. Normally I'd use 2 columns, perhaps 2 integers, and maybe a calculated column, such as ((ctxt(intcol1)+'.'+(ctxt(intcol2)) to arrive at that funky custno. But then I'd never combine the 2 id functions into one column anyway...
On Thu, Nov 18, 2010 at 6: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 > -- William Stacy, O.D. Please visit my website by clicking on : http://www.folsomeye.net and check out my new blog at http://drstacy.blogspot.com/
