>>Thanks Eric. I'll give that a try tomorrow. I had tried using ## on my recordset but not on the connection. When you say current transaction you mean only the one execution statement of the connection object? An additional execution statement (or in my case the utilization of the recordset) will count as another separate transaction correct? What if I use a batch (using commit and rollback)? Is that still considered to be seprate transactions even though all are submitted as a batch?
>
>I didn't used the correct word. I didn't mean Transaction in the sens of batch (using Commit).
>
>If you go to Query Analyzer, and you type all your queries into the same window placing a GO between each of them, these becomes "insolated queries that can't see what others are doing". When you are using multiple Execute or Open from VB, it is just like if you placed a GO between your queries.

Still, single # temporary tables are visible to statements in a batch on the session (or connection). For example, this works just fine from the QA:

Select * Into #myfaults From Faults
go
Select * From #myfaults Where fault_id<=20
go
Delete From #myfaults Where fault_id<=20
go
Select * From #myFaults