>Yes, of course, Mark, but as I mentioned earlier, my tables will never crash in edit mode. They either accept or reject changes made on views. One of the reasons I do it that way is that I leave it up to users to fill out most of the fields, except primary key of course, and they won't be able to save those changes until all required fields are filled out.

I'm afraid I still don't understand (and please bear with me). If you buffer tables, and apply the same restrictions to data entry as you do to your forms (all required fields must be filled, e.g.) then I can't see the advantage to using views exclusively.

Are you sure you're not talking about using unbuffered tables (which I would never do, either)?

>You also made a good point, one that I neglected to cover, in your previous posting, namely Client/Server applications.

This is the most frequent reason given for never using base tables, but it simply doesn't apply in all (or even most) cases. I would suggest that most databases are single-user, single-client apps for mom and pop businesses.

If you're working with medium to large-sized companies, then it makes sense to use views for everything, I suppose. Otherwise...