>Too bad, I strongly suggest views in that kind of situation...and any other, for that matter. Avoid direct use of tables; I don't have a single action performed directly at a table in several big applications (3.0 & 5.0). Its safer, easier to update/revert changes and, after all, what the views are for.

I don't see how views are safer or easier to update than base tables.

I use views where they are needed (i.e., when tables need to be joined), otherwise I use tables. If you're working on apps that may turn into C/S, then I can see using views exclusively; otherwise, I can't see the point when working with a single table.