Hey everyone, My apps are tiered having multiple UI, Facade, Business Logic, Data = Access layers usually. How do you typically handle errors in each = layer? Do you have SqlServer like error messages propagate up to the UI = or facade layer? Or do you have plenty of bool methods in the = DataAccess Layer indicating success failure and have it trap data store = specific errors? Or finally, do you created custom errors that are = specific to the layer but generic enough as to abstract the other layers = away from that layer's implementation. For example, a "DataStore = Unavailable" error thrown in the data access layer regardless of whether = it is a Sql Server "unable to make connection error" or even a file = access error if you have a xml file for a datastore?
Just curious and any advice would be appreciated, Daniel Wilson =================================== This list is hosted by DevelopMentorŪ http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
