Possible explanation: for some (not all) purposes, the number is handled internally using a "double" C/C++ type (8 bytes). The precision for "double" is 15 digits.

Vlad

>It appears to be 16, Vlad, in testing. Maybe the issue rises with the way the data is stored (char or int or num) or there is some translation between data types causing a rounding or display problem?
>
>
>>If I remember correctly, the precision in VFP is 15 digits.
>>
>>Vlad
>>
>>>I'm working with an old app written in FP2.6
>>>
>>>It uses a 16 digit number as the key field for accounts.
>>>
>>>This works fine as long as the account number does not end in 9. When I look at an account number in VFP that ends in 9, it's rounded up one number... this is bad!!!
>>>
>>>Even in a browse screen, I can be looking at the account number field and all the numbers look fine, but when I highlight an account number ending in 9, it's changed to the next highest number. Then when I arrow up or down off that number, it changes back to the proper number!
>>>
>>>What gives here ???
>>>
>>>As usual, TIA