>>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... <

Possibly ... haven't run into that yet though. One call seems to handle everything I've done so far.

>>I think this is some potentially cools stuff. However, it may be a PITA to do it in code. <

Dunno yet ... I'll let you know if and when we start messing with relations and stuff in the DataSet.

>>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.<

Yeah, this is more or less the way we've been doing things.

>>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 >...<

LOL!!

~~Bonnie