Your right ... remote views are very limited. But for the quick and dirty stuff like on-the-fly changing of data (like during test of applications in any language), they are great!!! The place I'm at now has data (in Oracle) in their development server that kept crashing my programs. Quick and dirty remote view (Outer Joins) found orphaned child records and orphaned parent records. The speed to create these joins in the remote view designer is much quicker then writing pass-through (after syntex errors).

For regular application development, 95% of the time pass-through is the way to go. I'm sure there are remote view designer sleuths out there that would disagree with us though. I've spoken to shops that only use remote views (never pass-through) and to tell you the truth, I don't know how they do it. But they do. They have hundres of remote views.

I personally think building the "WHERE" clause dynamically is the best way to go instead of having hundreds of remote views. But to each his own programming style.

>Don't take my reply wrong, I use Remote Views all the time. There are just some things that you can't do with Views, like nested selects, unions, updates, inserts and deletes all at the same time, returning multiple result sets, multi-table updates. You know, the advanced things that you would expect to be able to do with a "Big" back-end(I use Oracle and MS SQL Server).