>
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
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
