I have a table that contains, among other fields, a memo field.
Sometimes when a user edits a record in the table, they get the
following error:

"Error # 10030 Invalid Blob Handle for the table Wholesalers
specified".

The line of text that causes the error is this:

dmData.tblWholesalers.FieldByName('FieldMappings').AsString :=
FieldMappings.Text;

I have also tried:

dmData.tblWholesalers.FieldByName('FieldMappings').Assign(FieldMappings)

FieldMappings is a TStringList.

It will work fine 2 or 3 times, and then the 3rd or 4th time this
error is generated.  I then have to repair the table, which reports
the following problem:

"Invalid BLOB offset in BLOB file for physical record # 1 (logical
record ID of 1)..."


Delphi 7
DBISAM 4.22 Build 1

Any ideas?

Thanks.

Regards,

SteveG

Hi Steve,
>
> I have a table that contains, among other fields, a memo field.
> Sometimes when a user edits a record in the table, they get the
> following error:
>
> "Error # 10030 Invalid Blob Handle for the table Wholesalers
> specified".
>
> The line of text that causes the error is this:
>
> dmData.tblWholesalers.FieldByName('FieldMappings').AsString :=
> FieldMappings.Text;
>
> I have also tried:
>
> dmData.tblWholesalers.FieldByName('FieldMappings').Assign(FieldMappings)
>
> FieldMappings is a TStringList.
>
> It will work fine 2 or 3 times, and then the 3rd or 4th time this
> error is generated.  I then have to repair the table, which reports
> the following problem:
>
> "Invalid BLOB offset in BLOB file for physical record # 1 (logical
> record ID of 1)..."
>
>
> Delphi 7
> DBISAM 4.22 Build 1

It might be the same issue as

http://www.elevatesoft.com/scripts/incident.dll?action=viewaddr&release=4.22&type=f&incident=2157

Bernd Kuhlmann

Hi Bernd,

>It might be the same issue as
>
>http://www.elevatesoft.com/scripts/incident.dll?action=viewaddr&release=4.22&type=f&incident=2157
>
>Bernd Kuhlmann

Thanks.  I generally use my desktop PC for development (which has 4.22
Build 1) but was using my laptop this time.  I checked the version on
the laptop and realised that I hadn't upgraded it - it was still using
4.19.  Once I upgraded it the problem disappeared.

Geez, it's been one of those days.  

Regards,

SteveG