What I mean to say is that each enterprises needs are so varied that we can provide some aid in finding gotchas on a list like this, but you really need a thorough investigation into the requirements and find the right solution. Pat answers like "Never put the business logic in the DB" are rarely helpful in those situations, IMNSHO.
Thanks, Shawn Wildermuth http://adoguy.com C# MVP, MCSD.NET, Author and Speaker ->-----Original Message----- ->From: Unmoderated discussion of advanced .NET topics. ->[mailto:[EMAIL PROTECTED] On Behalf Of ->Franklin Gray ->Sent: Tuesday, September 13, 2005 6:10 PM ->To: [email protected] ->Subject: Re: [ADVANCED-DOTNET] Business logic -> ->""No technical or functional requirement, just a business ->one. This is the very nature of how business gets done and ->ends up with a myriad of different architectures" -> ->Wouldn't this be an example as to why not to put the BL in ->the DB? Never know when somebody is going to say "lets switch". -> ->=================================== ->This list is hosted by DevelopMentor. http://www.develop.com -> ->View archives and manage your subscription(s) at ->http://discuss.develop.com 09/13/2005 06:17:46 PM =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
