Tim - If I clear a Blob field record in DBSys and then run Verify, DBSys reports "BlobSize Mismatch ...".

The record's BlobSize is ZERO, but DBSys is representing the record as not Null (ie, as "(BLOB)" in the Grid).

Bill,

<< Tim - If I clear a Blob field record in DBSys and then run Verify, DBSys
reports "BlobSize Mismatch ...".

The record's BlobSize is ZERO, but DBSys is representing the record as not
Null (ie, as "(BLOB)" in the Grid). >>

Ignore the verify/repair error until B4 is released - it's another issue
with the repair incorrectly reporting a problem.  As for the BLOB size
issue, I'm still looking into a solution for that.

--
Tim Young
Elevate Software
www.elevatesoft.com

Bill,

I've also resolved the NULL issue.  I'll be issuing a new B4 shortly that
corrects both of these issues.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks, Tim.

Are these just reporting errors or corruption issues?

Jerry

"Bill Edwards" <sdbgrump@hotmail.com> wrote in message
news:8A96AF1D-8607-4C91-AD9F-8522A9FA50AE@news.elevatesoft.com...
> Tim - If I clear a Blob field record in DBSys and then run Verify, DBSys
> reports "BlobSize Mismatch ...".
>
> The record's BlobSize is ZERO, but DBSys is representing the record as not
> Null (ie, as "(BLOB)" in the Grid).
>

Jerry,

<< Are these just reporting errors or corruption issues? >>

In this case it's a reporting error.  However, prior to 4.28 B3, the repair
could both misreport and make some improper adjustments to the BLOB blocks.
Repairing the table with 4.28 B3 or higher will correct any issues, minus
this one case of misreporting.

I'm finishing up the 4.28 B4 release right now, and that should take care of
these issues for good.  Most of them are simply related to the repair not
coping properly with the new BLOB block design in 4.28.

--
Tim Young
Elevate Software
www.elevatesoft.com