>>>In your scenarios, could you make separate fill calls for each table in the dataset, always passing the same dataset to each subsequent fill call? Or, have you found it to be more efficient to make one call? <
>
>Oh, one call ... definitely!! You don't want multiple round-trips to the back-end if you can help it. Your SP returns multiple tables and fills each table in the DataSet.
>

Definitely one call would be better, but there is always the possibility that multiple calls can have a administrative payoff. i.e., if it eases certain coding burdens, then it may be worth it...


>>>Also, do you make use of the client-side features such as enforcing constraints,relations, RI, etc?<
>
>Haven't gotten that far yet. I'm not sure if we will or will not do this. So far, no, I haven't messed around with any of this yet.
>

I think this is some potentially cools stuff. However, it may be a PITA to do it in code. I am toying with taking a hybrid approach to things. Use the graphical designer for datasets and then to instantiate and populate the datasets in component code that is created sans a graphical designer.

>This is fun, John!! <g>

Well, it is more productive than some other "discussions" I have had lately...< vbg >... Then again, we are probably wasting our time with all this .NET stuff!! < gdr >...


>
>~~Bonnie