Hi Erik,

Why? Because, architecturally, it works better for me. I always use NoDataOnLoad and have a method called ViewsRequery that requeries the views as needed. There is no chance that View2 will go out of synch to View1. I can bind controls to View2 and not worry about it.

IMHO, you can get yourself into trouble with views working on views, but not if your framework is designed carefully.


>John- if it is not updatable, why do you need a view for this? There's a ton of trouble you can get yourself into by basing a view on a view, all avoidable by using SQL SELECT instead.
>