List, Without wanting to fire up a huge thread about MVC seperation etc etc. I just wondered if someone would share their expertise on the following question. Using Perrin's article on E-Toys is perhaps a good place to start. In the Model object which performs various DB procedures, what actions were taken if for some reason the connection to the database failed or if an SQL error happened? Was the whole "execute()" block put in an eval procedure and then a generic error page produced; Or were either per procedure evals or Exception objects used to propogate specific errors up to the control object so that it could display errors in the current page/view?
Richard