Remote views are driving me to drink!

I have established a couple of remote views in a new application. They connect OK and fill up with the appropriate data when procedures run. Occasionally, I get update errors related to 'attempted to insert a primary key field' at silly times like at a GATHER MEMVAR or LOCATE command (this being before a TABLEUPDATE() is issued).

I would like to use the view's fields directly on the edit screen and then have the table updated with the view contents.

What is currently accepted practice for using a SQL Server backend and local free tables together? The idea here is to have this application archive data from free tables used by an existing application into a set of SQL Server tables, then delete the records from the old system. The new application would then also allow maintenance of the archived records. The transfer of data is working correctly, and I see what I expect in the SQL Server tables when its done. The display and modification of the collected SQL Server data is the issue. I've always worked under the assumption that I can do any normal Foxpro table related commands on views too. Is this thinking wrong? If so, I have a lot of old code out there that needs rethought.

TIA!
Tom.