Thanks Sergey. That's a royal pain and still odd to me. The original VFP table was N(8), the new SQL table is numeric(8) but the VFP cursor is N(10).

As well, other than going through all the forms and explicitly stating the inputmask for all numerics, how do I handle this? I made the cursor updatable and the cursor field accepts 9999999999 since it's N(10) but a TABLEUPDATE() returns the following error because the value is to big for the SQL table.

Connectivity error: [Microsoft][ODBC SQL Server Driver]Numeric value out of range

>VFP stores Numeric data type in a table as a string. It requires 2 additional positions to store sign and decimal point.
>
>>Querying a SQL Server table using SQLEXEC() and I notice that every numeric field is 2 digits larger in the VFP cursor than the actual SQL Server table.
>>
>>If I look at the columns using the following 2 calls, I see that the VFP cursor is using the Buffer_Length and not the Column_Size.
>>
>>=SQLCOLUMNS(lnsqlhandle, "ADDRESS", "FOXPRO", "addsqlvfp")
>>=SQLCOLUMNS(lnsqlhandle, "ADDRESS", "NATIVE", "addsqlnative")
>>
>>Any suggestions on how to correct this behaviour?