I believe your right, which makes me wonder why M$ would reduce the precision by one digit???

Still, I'm stuck dealing with this issue. Is there any way I can force precision to 16 digits?

My code doesn't use any forms or controls so inputmask / format don't apply, I'm just using a numeric account number to seek child records... works in 2.6... doesn't work in VFP...

TIA

>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