M
Marty
Howdy All,
I recently asked about best practices in handling error
conditions. Steve Hudson (Word Heretic) responded with a
list of 5 rules, as follows:
rule 1 - avoid errors where possible through better logic
flow
rule 2 - always turn it off ASAP
rule 3 - always clear a handled err
rule 4 - handle all known errs, and pass all others back
to the UI.
rule 5 - batch mode needs to be more error friendly -
handle all
errors close to the UI.
These seem like sound procedures, although I'm not
entirely certain what "it" refers to in rule 2, "it"
probably means the error handling process itself.
However, I was wondering if anyone has come across
commercially available packages for VB error handling that
they think are worthwhile? Such packages are available
and easily found on the internet, but it is hard to
determine if any of them enjoy widespread use. Some of
these packages offer to make it easy to capture the values
of parameters passed to an error-producing procedure, to
shut down recordsets in an orderly fashion, and to
terminate any classes instantiated in the procedure. Do
most people employ such logic?
I recently asked about best practices in handling error
conditions. Steve Hudson (Word Heretic) responded with a
list of 5 rules, as follows:
rule 1 - avoid errors where possible through better logic
flow
rule 2 - always turn it off ASAP
rule 3 - always clear a handled err
rule 4 - handle all known errs, and pass all others back
to the UI.
rule 5 - batch mode needs to be more error friendly -
handle all
errors close to the UI.
These seem like sound procedures, although I'm not
entirely certain what "it" refers to in rule 2, "it"
probably means the error handling process itself.
However, I was wondering if anyone has come across
commercially available packages for VB error handling that
they think are worthwhile? Such packages are available
and easily found on the internet, but it is hard to
determine if any of them enjoy widespread use. Some of
these packages offer to make it easy to capture the values
of parameters passed to an error-producing procedure, to
shut down recordsets in an orderly fashion, and to
terminate any classes instantiated in the procedure. Do
most people employ such logic?
