Good practice for error-handling

Hello,
=20
I've been a bit unhappy with our error handling for a while. We've got a =
bunch of COM components using the ATL OLEDB wrappers exclusively to =
execute stored procedures.
=20
Sometimes the sp's are simple SELECT's, and sometimes they contain more =
logic. For the latter category, sometimes I feel like raising specific =
errors on sp-logic rather than referential integrity.
=20
How can I manage this? Does RAISEERROR come out as an HRESULT?
=20
Thankful for any pointers,
Kim

You can read messages from the OLEDB_DEV archive, unsubscribe from OLEDB_DEV,
or subscribe to other DevelopMentor lists at http://discuss.develop.com.