Yep, you've got it...



>Thank you Walter for the answer, Sergey for the KITN, and everybody else for your assistance.
>
>Apparantly, my testing wasn't as inclusive as it should have been - I focused on the data type more than the usage of parameters.
>
>If I understand correctly..........
>
>Using a ? parameter in the query causes SQL Server to execute a stored procedure. The SP runs in the equivalent of its
>own instance and, because I specified only #, the result set disappears when the SP ends. When I specify ##, the result
>set is visible to my VFP ODBC connection (and, I think, any other open instance of SQL Server) and disappears when
>all the instances that reference it are disconnected.
>
>Without using a ? parameter, the result set is created and, when # is used, it is visible only to the instance which created it.
>If ## is used, the same rules about open instances apply.
>
>Do I have this essentially correct?
>
>The implication is that I need to be careful about the temp table names when using ## because other users running the same
>code could create conflicts (Table Exists errors or overwriting the table or something like that) so I need to use SYS(2015)
>or some equivalent to create the temp table names.
>
>So far so good??????
>
>Any other tips (other than to really learn how to use the Profiler - thanks Walter) greatly appreciated.
>
>............Rich