Hi,
>I trap errors internally and store a negative value
>relative to the error to a propery called nReadyState,
>then set a property called lErrorOccured to .T.
>
>If lErrorOccured is True, then nReadyState will contain
>the error number for the error, otherwise nReadyState will
>be zero.
>
>Some of these DLL's use other DLL's, and sometimes they
>are used in applications.
>
>The question is this:
>
>When an error does occur under this scenerio, what's the
>best way to handle it and pass it to the applicaion?

IMHO this approach does not scale well. It needs the component to keep state for asking the error values from the app. I think it would be better to return evetual error states via another parameter in the calling method.

my 0.02 EUR

thomas