Asp on IIS->VB 6 ActiveX Dll components using ADO->SQL 6.5 Database stored
procedures.  I'm using many com dlls in order to comply with MS 3 tier
programming approach.

I'm trying to figure out the best way to handle errors in this project.
Currently I have error handlers in all of the public dll methods which
simply use the error object to raise the error back to the caller, which is
the asp page.

Is there a standard way of handling errors for this type of communication
flow?  I have read that some people always use one OUTPUT parameter in every
stored procedure and use it to return error numbers.

Thanks in advance.

Rob

In my opinion this isn't a bug, but by design, also it isn't because of ADO.
When you raise an error it means that you want to provide error-info to the
calling code. If you don't provide a source and/or a description they get
cleared out. The way I use to make sure the original source and description
'bubble up' is below.

tmpDescription = Err.Description
tmpSource = Err.Source
Err.Raise 635, tmpSource, tmpDescription

Edward Smit

...