Designing your application so that Stored Procedures are the only database objects that are accessed is generally the best practice. Agree? Disagree? Read this article by guest columnist Mindy Curnutt to see what she thinks!
My ASP file doesn’t access my database." "I can’t connect to my database from my code." "I’m having problems calling and debugging stored procedures." These are some of the problems I hear every day as a Microsoft® developer support engineer.
If you’re running database-intensive code from Visual Basic or ASP, stored procedures can give you a great speed boost. With ADO 2.1, one of the components that makes up MDAC, this technique is easier to implement than ever.
This article by David Rabb from the June 2001 issue of VBPJ shows you how to build a tool that will build a select, insert, update, and delete stored procedure for each table in a database. It's a great example of how to use DMO and a great tool as well!