You can reference the temporary table the same as a permanent one within the procedure. Your "SELECT * FROM #CashIn" would produce a recordset. Test it by running the stored procedure from Query Analyzer. If you need to deal with the rows one at a time, you could use a CURSOR (see books online) but then you could use the original SQL statement instead of the temporary table.

Still, if the logic of dealing with the output resides in a calling application (like a web page), you will want to use a DataSet object unless you create the ADOCommand object using the SQL statement instead of a table name.

There are many options. You might want to check out an ASP book too.

Guarddata-