> For example, with RV's, I have to give the user Delete, Select, Insert, and update permissions.

No, you don't. You give a component those permissions. Or if you want to use RV from the client, you give the application the login information. IMO, giving the user _any_ database password is not as good as giving them _nothing_.

I thought we just discussed this. Did I miss the part where you invalidated these points?

>So with security, I guess we are talking about degrees of security. But for sure, the security argument is not "simply incorrect"...< s >...

All of your arguments against RV with the security issue have been arguments against questionable practices that are not necessary with Remote Views. IMO, you still haven't given a single valid security argument against RV.

>>Your maintenance issues are arguable. I for one find having to maintain 3 different versions of SPs just so that I get "easier maintenance" and avoid the dreaded RV... well, it just doesn't make sense. To me. If you find it easier, that's fine, it is a "preference" issue.
>
>When you have the right toolset - maintenance is not a problem...

The same can be said for the RV strategy.