Rick Parrish:
> <rant>
> OLEDB is a fine example of an over-engineered interface
> model. That's why everyone uses ADO instead.
> </rant>
Its precisely because of the engineering in OLE DB that ADO can provide
an easy to use yet efficient facade over it. ADO Error objects are an almost
exact translation of IErrorLookup with VB/Automation friendly types. The ADO
Errors collection is a simple view over IErrorRecords. The basic model of an
error stack is maintained by ADO because it is useful.
> As for a nested error reporting
> mechanism, I would discourage people from returning an
> error message equivalent to "A error occurred at a lower
> level." If you can't contribute something meaningful to the
> error stack - leave it alone!
And if you can contribute something meaningful, then you should. It is
better to also maintain the lower level error as sometimes both the context
and the specific failure are needed to analyse the problem.
Neil
