Victor,

Since you're talking about CRUD operations and calling Stored Procs, I'm assuming you're talking about DataAccess classes when you speak of a controller object. Personally, I believe it makes sense to organize these objects functionally, so in the examples you mention Order and Order Detail ... yes, these should both be handled by one "controller object".

We take this one step further and have separate Biz objects and DataAccess objects. This way the Biz objects know nothing about the back-end data store, they just know to call a DataAccess class which takes care of getting/saving the data from/to the database.

We pass Typed DataSets back-and-forth between layers.

~~Bonnie