I considered that, but I really don't want to return any more data than I need to.



>You can return number of parts per product as part of your select statement and also the number of unique products.
>
>>I have a stored proc that returns the result of a JOIN from a SQL Server database. The data represents products and parts. It's possible to have one or many products returned, and all the parts that correspond to each product. So it will either be a many to many, or a one to many.
>>
>>Once the data is in ADO, I want to be able to determine of I got back more than one product. So far I have to following code, but to me it seems rather inefficient:
>>
>>

>>bool bMultiProductDS = false;
>>
>>// Get the first prod number
>>string sFirstProductNumber = dsResults.Tables[0].Rows[0]["Product_Number"].ToString().ToLower();
>>
>>// Define a variable to hold subsequent product numbers
>>string sNextProductNumber = "";
>>
>>// Define a row counter
>>int iRow = 0;
>>
>>// Loop once for each row in the firs table
>>foreach(DataRow oRow in dsResults.Tables[0].Rows)
>>{
>>    // Skip the first row
>>    if (iRow == 0)
>>    {
>>        iRow++;
>>        continue;
>>    }
>>
>>    // Get the next product number
>>    sNextProductNumber = oRow["Product_Number"].ToString().ToLower();
>>
>>    if (sFirstProductNumber != sNextProductNumber) ;
>>    {
>>        bMultiProductDS = true;
>>        break;
>>    }
>>}
>>