>>How do you manage the modules? Is each module its own project in a solution?
>
>Typically, yes. Further broken down by layer.
>
>So, you'd have projects like: Business.Customer, DataAccess.Customer, DataSets.Customer and WinUI.Customer for example.
>
>~~Bonnie

Excellent. I like this model. Seems easy to manage. Couple questions:

1) Each layer resides in is its own project? If so, would all 4 of these projects be part of a Customer solutuon, which then becomes part of the app's solution?

2) It looks like a 'chain' of usage, IOW, WinUI.Customer uses Business.Customer which uses DataAccess.Customer which uses DataSets.Customer. Am I on track here?

3) DataSets.Customer contains typed datasets?

4) Finally, I'm having a hard time visualizing a need for a BO layer in my app. Part of me wants to create it anyhow in case it's needed later, and even more just to segment things. What kinds of things do you put in your BO's?

Thanks! I'm actually starting to understand all this. :)