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

I'm just interested how did you implement DA. From what you're saying it looks to me that DA class should be smart enough to be generic and handle anything regardless of particular Biz Object.

That's why I want to understand what do you have there and what do you call a DA class.