RepairTable produced a bunch of messages like this:

Invalid BLOB offset in BLOB file for physical record # 2375, error fixed...

Is there a way for me to use the record# above to extract the
information that was in the memo file, if I have an old backup?

(dbisam 2.12)

Jerry

"Jerry Blumenthal" <jerry@blumenthalsoftware.com> wrote in message
news:022F1E4D-BA07-4B7C-97C2-D272BC17665B@news.elevatesoft.com...
> RepairTable produced a bunch of messages like this:
>
> Invalid BLOB offset in BLOB file for physical record # 2375, error
> fixed...
>
> Is there a way for me to use the record# above to extract the information
> that was in the memo file, if I have an old backup?
>

What do you have now in the blob field? Null? If so, just update using SQL,
matching id fields from oldtable and newtable, WHERE newtable.blob = NULL

Robert

> (dbisam 2.12)
>
> Jerry

Jerry,

<< RepairTable produced a bunch of messages like this:

Invalid BLOB offset in BLOB file for physical record # 2375, error fixed...

Is there a way for me to use the record# above to extract the information
that was in the memo file, if I have an old backup? >>

With 2.x, if you define a table with no primary key, then the table will be
in physical record # order.  Therefore, if you simply remove any primary key
from the table, you can navigate directly to the record #'s that appear in
the log and use that to repopulate the BLOB fields, provided that you have
the data that was supposed to be there.

--
Tim Young
Elevate Software
www.elevatesoft.com