>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 ?

The difference is that SQL Server thinks byte 31 is both the sign and part of the value. VFP considers it to be only the sign.

Which is correct? Both. Not knowing what it would take to bring VFP in-line with SQL Server, I can't say.