I think maybe I just don't know the difference between a request error and an 
exception error.  Could someone explain that?

The reason I'm confused: Recently I had a problem with an address text feild.  
People kept putting # in it for their apt. number.  I put some code in place to 
check for and remove any char. that I don't want.  However, until I did that 
the app. would throw a request error with absolutly no usable debugging.  And 
worst of all, it wouldn't send me an email.

Currently I have another app. that runs through a DB table full of stored 
emails (rows include: to, from, subject, body, DTS).  This is ran by a 
scheduled task every hour.  What happens when a user wants to use 2 email 
addys?  They put in two email addys w/out seperating them, thus breaking my 
scheduled process.  grrrr.  But, until I set up a try/catch solution, I had no 
way of knowing that they had done that until A. my users start complaingin or 
B. I check it every hour or so.

I just thought it would be a hell of a lot easier to setup something in my 
application.cfm file that sends me an email for every error message thrown by 
any user at any time.  I could also use this to detect early on if I had 
something broken that I wasn't able to catch in the debugging process.

Thank you,
Clint

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Find out how CFTicket can increase your company's customer support 
efficiency by 100%
http://www.houseoffusion.com/banners/view.cfm?bannerid=49

Message: http://www.houseoffusion.com/lists.cfm/link=i:15:1334
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/15
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:15
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.15
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to