Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Apr 27, 2006 11:53 AM by mikener
Apr 27, 2006 11:53 AM|LINK
This article raised a few questions that I was hoping you could answer for me.
1. The article implies that for every business entity that you should have one corresponding Data Access Component. Is this correct or do you have one large Data Access Component that spans many business classes?
2. If you do have one Data Access Component for to support each business class, would it be better to put each Data Access Component in a separate assembly or all of your Data Access Component's into one big assembly?
3. I have many Web Forms that are not used for business processing, but to load up database tables with what my company calls static data (i.e. a table for company locations, a table for company products... etc) For each these data centric processes
I generally have a one to one relationship between the web form and the database table that the web form supports. I was planning on creating the following 2 classes per database table. 1) An entity class that has properties that map to the fields in the
table. 2) A Manager class that performs all CRUD operations on the table. Is there a better way to do this (i.e. would I be better off using typed datasets or some other method)?