Peter,

Don't know why I didn't think to suggest that. Doh! Depending on what you're doing, a stored procedure is usually better anyway ... keeps all the data access stuff with the back-end that way.

Glad you finally worked it out!!

~~Bonnie


>Actually, I came up with a different idea that works fine.
>
>Instead of using a SQL Server view, I created the equivalent SQL call as a SQL server stored proc.
>
>So now, instead of going through 3 layers, VFP SQLPT Cursor->SQLServer View
>->SQL Server Table, it's straight from the VFP SQLPT Cursor to the SQLServer table, which seems to agree with VFP, since it now, with no further ado (?), produces the correct results.
>
>Thank's people!
>
>>before you make Insert/Replace, open a new SQL connection handle,
>>and close the handle after made the operation.