I have researched the view and found that the ID Number field that VFP is trying to update is an ID number from a different view on a different table!! That ID number does NOT exist in the view I am trying to update, yet I get that error (which is a good thing I think because it is the wrong ID number).

If you are getting the primary key value from sql*server and using the @@ command to retrieve it, beware that if you have insert/update triggers that create records in other tables (like audit tracking) then this could give you the those table's ID values instead (ok -- I only read about this on UT, I am still setting the primary key from a last used id table)

Kevin