>Hi Mike,
>
>Thanks for responding!
>
>This application is a multi-user app with a good chance of user collisions. So, when I update the 'view' with tableupdate() I should check for update errors at that time for the base table? Also another thought is if the base table is buffered and there has been some updates to that buffer, and at the same time the view is modified and tableupdate() is issued, it sounds like I could possibly have an update conflict to deal with when I issue a tableupdate() on the base table. Is that right? Would it be less confusing to take buffering off when using an updateable view?
>
>I hope this message makes sense. I'm having trouble understanding this.
>
>Thanks,
>
>John

John,

How about this - when you use a view, ignore the base table. If an update conflict or any other error occurs, VFP will let you know. TABLEUPDATE() will return FALSE and you'll be able to query the error using AERROR()

I like to think of a view as a 'virtual table.' It is an entity upon itself.

-Mike