First, check your base tables, and view definitions to see if there are any rules or triggers which -- will cause the record pointer to move. If you have any rules like that, you'll have to move them to execute prior to your telling the DBC to save.

I also ran into this in another situation, which usually causes a "Cannot insert empty row into base table" error. The view that was failing had inadvertantly brought a field -- which I intended as a read only field from another table -- and made it updateable. I have a RECID() function on that other table, which fired, and this caused the problem.

In the view designer, or in code generated by GenDBC/GenView, check to make sure that only the fields you want updated are checked.