That can be a problem! Just added the value -2,147,483,648 to an int field on SQL server and ran a sql pass-thru query in VFP against that table and the field comes back as an int in VFP but contains **********

This is a pretty big compatibility issue! Do you think it should be fixed by the VFPT ?

>>So why is that SQL Server integer definition is:
>>
>>integer or int
>>Has a length of 4 bytes, and stores numbers from -2,147,483,648 through 2,147,483,647.
>
>It's probably handling the math slightly differently. Consider that -2 ^ 31 = -2,147,483,648 and 2 ^ 31 - 1 = 2,147,483,647. This is how SQL Server defines an integer. VFP does the subtraction on both equations not just the one, reserving that for zero.