>>>>Hi,
>>>>
>>>>I am trying to better understand the basics of 3-tier design. I am actually refactoring my VFP application to be a 3-tier design but prefer to ask general question(s) on .NET forum.
>>>>
>>>>In the 3-tier application you have a bunch of BIZ objects, for different entities. That is clear. Is it correct to assume that there should be only one DA object that all BIZ objects use to update the database?
>>>>
>>>>(Side note. In my VFP application no matter how I try I can't seem to design it this way. So, so far, I end up having a separate DA object for each BIZ object. This is probably wrong but I want to be sure).
>>>
>>>Each Biz Object will use its own dataset, if this is the question.
>>
>>This wasn't exactly my question. Dataset is a mechanism of sending data between tiers (specific to .NET world). My question was more generic.
>
>What exactly do you have in your Data Access class?

First, the word I should have used in my reply is "general" instead of "generic". Anyway, it is not important what specifically I have in DA class. But generally speaking I have code there that saves user changes and/or additions to the database. And what I find - as I stated in my initial message - is that I am creating a separate DA class for each BIZ class. And I wanted to know if this is a problem in a "good practice type" 3-tier design approach.