Hi Mark,

No, it's available to any connection and exists as long as there's some connection referencing it. I use it by creating a table of matching primary keys from VFP and then calling Crystal Reports to do the appropriate selects based on those primary keys. It means that the users get great control over what data they want presented and how it's presented (from Crystal reports) and I get great control over which records actually match their criteria.

Cheers,

Andrew

>Hi Andrew,
>
>Is that temporary table available ONLY to that user (connection)?
>
>Thanks, I'll look into the # and ## symbols.
>
>
>
>>I do something similar to this by creating a temprary table on the SQL Server. The table exists only as long as the connection that created it. In all other respects, it's a standard table. The way to create it is to use the # sign at the start of the table name (or perhaps it's two # signs - you'd better confirm that. One way the table lasts as long as the connection's open, the other one is more short-lived).
>
>>You can INSERT INTO the temporary table and use it in SQL statements etc.
>
>Cheers,
>
>Andrew
>
>>We're converting our VFP app to a dbc-less VFP -> SQL Server application. On one of the forms, during a data entry session, the user adds new customers. One requirement is to keep track of the customer records added during the data entry session so that the user can go back to any of those records during the session. The implementation before was to store the keys in a cursor, then when the user wanted to see a list of those they added during the session we'd do a SELECT joining that cursor with the customer table.
>>
>>Now, using SQL passthru (no DBC, so no views) any suggestions how to provide that same functionality? We've discusses a number of ideas, but looking for other suggestions. We don't want to bring down the entire customer table from SQL with passthru.
>>
>>Thanks.