On Fri, Oct 8, 2010 at 10:32 PM, lauhw <[email protected]> wrote: > By right, your program should handle all the exception that has been > raised during the runtime. For example, what if "Scon.Open();" raise > failed to connect to the database server or failed to execute the > command due to typo-mistake in the sql statement. > > In my program, i save all the exception into an error log file or > database and use it for the purpose of debugging and user support. ---------------
What do you present to users to let them know? Writing to a log sounds great, and if Scon.Open fails how are you then going to write the error? Trap for .Open and post that to Log otherwise post to database? I am in the start of laying this out for one of my apps as well. Not a fan of using the LOG because the production server logs are not available for me to view. So what to do? Make my own XML file to post to and have a secure page that reads it? -- Stephen Russell Sr. Production Systems Programmer CIMSgts 901.246-0159 cell
