In the original discussion about missing BLBs
http://www.elevatesoft.com/scripts/newsgrp.dll?action=searchopenmsg&group=5&msg=59824&keywords=BLB

Tim suggested "All you need to do is copy over any blank .BLB file to the same root name
as the table name."

This is the fix that I want to implement in our product. But after analyzing BLB files
from different tables I can see that they are different. Each of them has a different
value in the first byte. I tried copying and it does work fine, but the question is - IS
IT SAFE? What info do you have in the first byte of BLB file? Can I copy empty BLB file
from one table to another table even though their first bytes do not match?

Alex,

<< This is the fix that I want to implement in our product. But after
analyzing BLB files from different tables I can see that they are different.
Each of them has a different value in the first byte. I tried copying and it
does work fine, but the question is - IS IT SAFE? What info do you have in
the first byte of BLB file? Can I copy empty BLB file from one table to
another table even though their first bytes do not match? >>

The first 4 bytes are an update stamp, and can be any value as far as DBISAM
is concerned.  The update stamp is simply an incrementing counter that is
used to determine when changes are made by other sessions.

--
Tim Young
Elevate Software
www.elevatesoft.com