There's nothng wrong with sending 60 or 70 parameters to a stored procedure and letting SQL Server do the insert. It's a good idea to minimize the number of network trips.

What I'm not a fan of, is making the direct database calls from within ASP.

You might give this a quick scan:
http://msdn.microsoft.com/architecture/patterns/ArcThreeLayeredSvcsApp/default.aspx

-Mike


>Sorry to be a pain but I'm new to ASP and SQL server. What is WinDNA?
>I'm just sending data from a form with 60 or 70 fields on it to a sql database. In this case I figure I might as well just send all of the values to one stored proc which will do all of the insertions.
>
>Phil.