Hi Tim,

If a stored procedure is called that doesn't have a field that the client app is expecting, only a general EDatabase exception is raised.  There is no EEDBError exception.

Would it be possible to add an exception for this so that I can test for it?

For example:

    if (EEDBError(E).ErrorCode = EDB_FIELD_NOT_FOUND) then

Thanks.

= Steve

Steve,

<< If a stored procedure is called that doesn't have a field that the client app is expecting, only a general EDatabase exception is raised.  There is no EEDBError exception.

Would it be possible to add an exception for this so that I can test for it? >>

This is handled at the TDataSet layer, which is why you're seeing a general EDatabaseError instead of a specific EEDBError exception.

Tim Young
Elevate Software
www.elevatesoft.com

<< This is handled at the TDataSet layer, which is why you're seeing a general EDatabaseError instead of a specific EEDBError exception. >>

Ok, thanks Tim.  I've done a workaround by parsing E.Message.

= Steve