Is this a plant? Are you looking to start a fight?

Well, I'll answer anyway.

My .00001 cents on this issue is, yes, use stored procedures as a standard method of development. First off, you get more granular security through the stored proc than you can through VB code. Second, you get more modular code by putting the code for database access into the database itself, allowing you to make changes to the internals of a query without having to redeploy the app.

You'll hear that performance will change in one direction or the other. That's not entirely true. If a reusable execution plan is generated from code or from TSQL, it doesn't really matter.