Nancy and Mark,
Thanks for both your suggestions. However, SET DATABASE TO and REQUERY with specified-alias does not work. This is the strangest problem I've ever encountered with VFP! Usually, it's some logic error (which is of my own doing) and can debug it in few hours or at least in a day or so. This, however, got me totally frustrated. It's not like I don't know how to work with views since most all my forms use them (almost exclusively) but...

The only workaround (hope temporary one) is to open the table directly and use it to add new recs OR create a duplicate view (identical in every way) and use it to add new recs. Pretty weird.

>John (and Mark):
>
>Mark's comment is interesting (about SET DATABASE TO). I've never had this problem, even when in applications that used multiple DBCs, but I _always_ include the alias name in Tableupdate, TableRevert, Requery. Actually, any function that takes an alias! Not only does it help avoid a common "assumption" but I like how it is self-documenting.
>
>BTW, you can very easily have tables open (and their DBCs) w/o any DBC being the SET dbc.
>
>>When I add and change records in a local updateable view and issue =TABLEUPDATE(.T.) and then REQUERY(), why do I get this error? By issuing =TABLEUPDATE(.T.) prior to REQUERY(), shouldn't the view's data be updated and buffer committed?