>The bottom line - if you are doing C/S work of any significance - and if you are using RV's - in the long-run, the chances are good you have shortchanged yourself. A hypo:

PMFJI - but to add to your point JVP - and directed to John Ryan -

1 - I believe not enough has been made of the DBC factor. Having to use a DBC in a client-server situation is an uneccesary PITA at best.It is high on my list why I stay away from views. Think about what your are saying - "I must have a client side database so I can access my server database" - kind of silly in my opinion.

2 - Also - you get a LOT better control with the SPs - and I KNOW a lot better performance on complex multi-table join selects statements. The fact that I can "hot swap" front ends so much easier is enough of an argument there.

3 - I am a stubborn "always right until proven wrong" kind of guy, but I am open to changing my mind with no bruised ego when I am wrong. Only a few years ago I was a "RV Evangilist" - after a couple of projects - I RAPIDLY saw the value of SPT cursors, Stored Procs, and rolling my own data management objects. JVP is 100% right when talking about flexibility and the ultimate cost - especially in this day of distibuted computing, multiple front ends, and the web.

HTH,