>>So you are saying that the following sequence of SELECTs can be sent one after the other to SQL Server and I can expect to get the result I need...
>>1) SELECT 7 fields from 2 tables based on JOIN/WHERE.
>>2) Using 1 of those 7 fields, SELECT those fields and 2 others from another table.
>>3) Using one fo those 2 fields (of the now 9 fields), SELECT using a correlated sub-query on another table.
>>4) Using the result set from the last SELECT, run another to get the final bits of data I need.
>
>Of course, you have to code them properly, so that the results of query 1 go into a temp SQL server table that query 2 can use and so on, until the final query's result set is sent back to the client.

Ahhh, totally unaware that I could store stuff in some "temp" SQL Server table for later re-use. Wouldn't there be a possible conflict if 72 users were doing similarly all at once?

>
>>Or maybe I can send them all and just sit back and wait for the result set(s)?
>
>Actually, sending them all in one batch would be more efficient.
>
>Of, as I said, option 3 is making your four VFP queries into a single T-SQL query.

That's what I have in mind but I ASSUME that this is as a stored procedure, yes?

thanks again


>
>>thanks so far.
>
>Sure,
>BOb