Stefan wrote >So, there were, >for instance, auxilliary classes showing up to model many-to-many >relationships! This is what I mean by 'being able to seeing the database >through all layers'. This is what I consider 'bad design'.
I would like to hear what you consider a 'GOOD Design!' approach for many to many relationships and Application code. I have designed several systems (f.e. Financial Protfolio) where exposing this M 2 M relationship was the very center what the application did. Without having the Many to Many relationships C.R.U.D. in application it (the application) would have had no business value for the customer. If I am not understanding your point on the "Bad Design" then please help with a better definition. [EMAIL PROTECTED] =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
