Handling SQL Error
I have a some self-service applications that access MSQL databases, and if there is an error I will just bail out to customer service rep. However I working on a customer service survey application. That reads that question from a database one at a time and writes in the a customer ranking. I'm looking for the best way to handle dbwrite, dbread, and dbget erros and keep on moving.
- Forums Topic:
Recommended Reading:
Handling SQL Error
If I understand this right, you are better off reading all the survey questions from the database at once and loading them up into an array and then writing them back to the database, If the write fails you can either write them to the local harddrive of the UCCX box in a comma delimted text file and/or email them to yourself saying "error writing to DB for customer <blah> and then list the results"