All the ideas so far sound pretty good to me. One other possibility is to create a variation of the stored procedure that returns the JOIN which just returns the count of unique product id's. You could just set up an bizobj.ExecSprocScalar() to get that value.

You may already know this but I just recently learned that the foreach loop does take advantage of indexes and is quite fast. For old FoxPro programmers, it messes with our heads but I've been told to think of the foreach as closer to a scan or seek. That made me feel less uncomfortable with that option. It is still a lot of code just to get a count, though.

>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;
>    }
>}
>