J
Jay B. Harlow [MVP - Outlook]
Scorpion,
If the users (accounting department) are not able to show you (reproduce)
what is happening, so you can debug it yourself & see the variables.
I would put a try catch around that section of code, and write the sql2
variable, plus any other pertinent information (custno, opentype, sortterm,
Exception.ToString) to a text file or event log. In fact you could create a
custom Exception that includes all the pertinent information, then let your
normal exception logging handle it. Then when they say it happened, I would
check the text file or event log & say: Oh! Item x is wrong...
As the others have suggested. I would also look at parameterizing the SQL
statement rather then using string concatenation.
Hope this helps
Jay
If the users (accounting department) are not able to show you (reproduce)
what is happening, so you can debug it yourself & see the variables.
I would put a try catch around that section of code, and write the sql2
variable, plus any other pertinent information (custno, opentype, sortterm,
Exception.ToString) to a text file or event log. In fact you could create a
custom Exception that includes all the pertinent information, then let your
normal exception logging handle it. Then when they say it happened, I would
check the text file or event log & say: Oh! Item x is wrong...
As the others have suggested. I would also look at parameterizing the SQL
statement rather then using string concatenation.
Hope this helps
Jay
