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?