Using DBIsam v4.29 build 4...

I have this bug report data (madexcept) from a customer:

exception class   : EDBISAMEngineError
exception message : DBISAM Engine Error # 9479 The table 'Table_OutGoingFax'
is full and cannot contain any more data.

main thread ($2d0):
00a1929b +017 SF5.exe    dbisamtb  2935   +1 DBISAMError
00a61bcb +087 SF5.exe    dbisamen  5478  +19 TDataEngine.RaiseError
00ab6e4c +094 SF5.exe    dbisamen 42040   +2 TBlobFile.CheckMaxBuffers
00ab69f9 +0ad SF5.exe    dbisamen 41913   +5 TBlock.PutBlockData
00a69c82 +01a SF5.exe    dbisamen  8633   +1 TBuffer.Initialize
00ab676c +024 SF5.exe    dbisamen 41873   +2 TBlock.Initialize
00476c26 +02a SF5.exe    Classes   2924   +7 TList.Add
00a6a3e0 +03c SF5.exe    dbisamen  8907   +7 TBufferedFile.GetBuffer
00a79f55 +02d SF5.exe    dbisamen 16513   +1 TDataTable.GetBlock
00a7f551 +031 SF5.exe    dbisamen 18983   +2 TDataCursor.GetBlock
00a7f4f5 +021 SF5.exe    dbisamen 18964   +1 TDataCursor.GetNextFreeBlock
00aa929c +224 SF5.exe    dbisamen 37388  +49 TDataCursor.WriteBlob
00aa9fdb +15f SF5.exe    dbisamen 37800  +31 TDataCursor.FlushBlobBuffers
00a9b58e +5fe SF5.exe    dbisamen 31175 +128 TDataCursor.ModifyRecord
00a238c8 +040 SF5.exe    dbisamtb  8967   +5 TDBISAMDataSet.InternalPost
009e63a9 +029 SF5.exe    DB       10816   +5 TDataSet.CheckOperation
009e6044 +048 SF5.exe    DB       10673   +7 TDataSet.Post
00a23a7a +00a SF5.exe    dbisamtb  9024   +1 TDBISAMDataSet.Post


The process here is importing data from .dat files in DBIsam Version 3 to
DBIsam Version 4.  What I'm doing is
copying the .dat, .blb and .idx files to a work directory, changing the file
extensions to .sfdat, .sfblb, .sfidx and
then upgrading the table using sql then importing the data into the version
4 table which has already been
created.  The sql that creates the table being imported into was created
with the default blob block size.  There
are 3 blob fields but the original tables upgraded from version 3 of dbisam
(the source table in the import) only
has 1 blob field.

Is the blob block size the problem here or is it something else ?  I know
the source table is nowhere near capacity.

The blob field stores a tiff file which is a typical black and white image
of a faxed page.  The image size of one
page would be 1728 by 2236 pixels, the tiff file will be at least 1 page but
perhaps many pages so it's not possible
to say how large a typical blob would be.  What is the best blob size for me
to use when creating the destination
table for this type of blob ? (if this is even the problem here)

Thanks

John Taylor