thanks for the replies. to expand the query further what i was thinking of was splitting our code up, again to best practice standards, using objects. what we would have is a business function layer that would take input and then pass it to stored procs to save it into the tables after some validation. would it be best to have just one stored proc to save a transaction that would update several table or have one stored proc for each table and posibly call it multiple times.
~M


>---Using stored procs is considered a "best practice".
>
>Absolutely agreed.
>
>And I wonder whether this will fly in [or below] the radar of those who disagree.
>
>Kevin