>Chris,
>
>>>I would say it depends on what you are going to do with the data and how much of it you have. If you have a parent detail relationship where there are a lot of child records to each parent I would go with separate datasets and pull new detail with each skip through the parent.<
>
>In this scenario, I would *still* go with one dataset, three tables. You would not (or at any rate, should not) be pulling in multiple parent rows. One row in the parent table, then only related rows in the child tables.
>
>~~Bonnie
>

So then what would you do if you wanted to show all of a customer’s orders and let them scroll through the list to see the details?
How would your application benefit by avoiding multiple parent rows?