The DAL shouldn't be setting anything in yout BL. In fact, your DAL has no reason to ever directly call your BL. (Indirect calls though interfaces by raising event can be useful for error handling and flow control, particularly in an asyncronous multi-threaded app, but I digress.)
A better design is to have your BL call the DAL layer to get data, then the BL, and only the BL, sets its private data accordingly. Then your UI layer displays what is in your BL. The BL provide readonly properties for the data the user can only look at, and methods and read/write properties to access and modify the rest of the data. - R.B. Davidson On Feb 15, 10:24 am, Adam <[email protected]> wrote: > Thanks for your reply. > > The problem is that if I make the property set method private/non- > existant then the DAL cannot set that property from the database in > order to return the populated object. > > Adam
