I have run into the exact same error, although the cause may be different. In my remote view, I was doing an APPEND BLANK (as the Business Object does), filling in some of the fields, then issuing a TABLEUPDATE(). The error occurred because I did not have all the fields filled in (and no defaults for the table in SQL Server). I should have known that SQL Server does not behave like VFP: if you don't have explicit DEFAULTs for you columns, you have to fill in every field in your view.

>Hmmm, thanks for your reply, I'll keep trying to get it to work the first way. I'm having some success that way but I think I'm doing a couple things wrong. The error I'm getting is 'Cannot insert an empty row from a view into its base table(s)'. Sometimes when I'm editing it does work now though. I'll keep trying...