I've been fighting this same issue for a couple of weeks now. I'd looked at the buffering, RO, EOF() and other issues people have suggested here. I just went back and changed the way in which the view is constructed. It was a 3-table join using LEFT OUTER JOINS. I manually reconfigured them to be INNER JOINS and voila - the save now works. I wish I was genius enough to give you a full 'splanation of what happened, but I'm not that good of a theoretician. I wanted to get this to you ASAP so you could see if that might be a place to fix your problem as well. I'll go back and detail exactly what I did so that someone who understands VFP under the hood better than I might come in and enlighten us.

HTH

Update on April 24, 2007:

Here's the SQL join section for the view that did not update properly:
FROM ;
trainerbuilder!profiledx ;
LEFT OUTER JOIN trainerbuilder!profiles ;
ON Profiledx.iprof_key = Profiles.iprof_key ;
LEFT OUTER JOIN trainerbuilder!dx ;
ON Profiledx.idx_key = Dx.idx_key;

And here's the view that did update properly:
FROM ;
trainerbuilder!profiles ;
INNER JOIN trainerbuilder!profiledx ;
ON Profiles.iprof_key = Profiledx.iprof_key ;
INNER JOIN trainerbuilder!dx ;
ON Dx.idx_key = Profiledx.idx_key;

I welcome anyone to explain the distinction so we can understand it more clearly.