Why is the ErrorDatabaseName property of EDBISAMEngineError always blank?

I used to catch and handle table corruption exceptions (using RepairTable)
but that doesn't seem to work now becuase the ErrorDatabaseName property is
always blank.

Thanks,
Danny

Danny,

<< Why is the ErrorDatabaseName property of EDBISAMEngineError always blank?

I used to catch and handle table corruption exceptions (using RepairTable)
but that doesn't seem to work now becuase the ErrorDatabaseName property is
always blank. >>

What error code (or codes) in particular are you referring to ?  That way I
can cross-reference them and see whether or not they populate the database
name.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

I am trapping these:
DBISAM_HEADERCORRUPT
DBISAM_MEMOCORRUPT
DBISAM_INDEXCORRUPT
DBISAM_INVALIDBLOBOFFSET
DBISAM_READERR

Thanks,
Danny

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:0ED0B815-8A1A-48B3-9B4A-B20871B825C3@news.elevatesoft.com...
> Danny,
>
> << Why is the ErrorDatabaseName property of EDBISAMEngineError always
> blank?
>
> I used to catch and handle table corruption exceptions (using RepairTable)
> but that doesn't seem to work now becuase the ErrorDatabaseName property
> is always blank. >>
>
> What error code (or codes) in particular are you referring to ?  That way
> I can cross-reference them and see whether or not they populate the
> database name.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Danny,

<< I am trapping these:
DBISAM_HEADERCORRUPT
DBISAM_MEMOCORRUPT
DBISAM_INDEXCORRUPT
DBISAM_INVALIDBLOBOFFSET
DBISAM_READERR >>

These codes do populate the database name:

DBISAM_HEADERCORRUPT
DBISAM_MEMOCORRUPT
DBISAM_INDEXCORRUPT
DBISAM_INVALIDBLOBOFFSET

This code does not:

DBISAM_READERR

--
Tim Young
Elevate Software
www.elevatesoft.com