>>If you created a temp table in SP, you can not access this temp table outside the SP.
>>
>>That's not entirely correct. If I start a transaction from .NET, and that transaction runs stored procedure A (which creates temp table ABC), and then runs stored procedure B, stored procedure B will see the temp table.
>>
>>Temp table scope is based on connection, not a single stored procedure
>
>Please see my question about SCOPE_IDENTITY
>
>This is getting me thinking that my problem may be I need to wrap my insert and my call to scope_identity inside an explicit SQl transaction since without it from VFP each SPT call is going to get its own implicit transaction.
>
>Let me know if that makes sense in the context of the problem I'm outlining.
>
>TIA

Yes, that's exactly what is happening. I always put both commands together

insert into ...
select SCOPE_IDENTITY()