Writing to SQL under commitment control

[Matt Clepper]

Ok - debated on posting this on SQL group but here goes...

I have a piece of ASP code (function #1) that creates a new SQLTransaction
(BeginTransaction) to and begins to write records to the database under
commitment control. Function #1 then calls a series of other functions
(sub-functions) where I would also like to write transactions under the same
commitment control. After I start writing records, if anything fails
anywhere in any function, I would need to roll back any transactions that
have occured in the previous Function #1 or and previously successful
sub-functions.

Here are my questions/issues?

1. I don't believe the records I write in the sub-functions can be under
the same commitment control I started in Funciton #1 - true? If I'm wrong on
this, please tell me how I can make this work.
2. If the sub-function can't write under the same commitment control, I'll
want to process information in the sub-functions and pass back to Function #1
to actually write them. What would be the most efficient means to do this?
The size (# of rows) that the sub funciton will send back is variable full of
multiple data types. I assume I could write everything processed in a
sub-funciton to a temp table and have Function #1 read and write these under
a single commitment control - I just hate to write to the DB twice.
Transaction volume here is high so every bit counts.

Any help appreciated...

Thanks! -Matt