I am trying to convert data from Act 2000 to a MySQL database. I have successfully imported DBF files to separate MySQL tables. However, I am having problems with a file *.BLBthat appears to be a non-standard memo file.
DBF files identify as dbase III Plus, No memo format. There is one *.BLBthat is a memo file for multiple DBFs for sharing BLOB data.
If you read this document: http://cicorp.com/act/sdk/ACT6-SDK-ChapterA.htm#_Toc483994053 )
You can see that the column REGARDINGhas 6 characters. Description: This 6-byte field is provided by the system and contains a link to the field in the Binary Large Object (BLOB) database.
Now, after opening *.BLB, I see that the block size is 64 bytes. All text blocks are NULL padded with this size.
When I stumble, we try to convert the values stored in the REGARDING column to lock the location in the BLB file. My guess is that the 6 character field is an offset.
For example, one value for REGARDING (ignoring square brackets): [ ",J$]
In my Googling, I found this: http://ulisse.elettra.trieste.it/services/doc/dbase/DBFstruct.htm#C1.5
, memo ( , DBF) (.. ).
, ( , ) [",J$] BLB . , ACT2000, /MySQL BLB.
, , DB REGARDING [ ",J$] 1024 ( 16 , , , 64 ).
Python , DBF, .
, , , .
64 , DBF?
, , StrToInt64, blob. 64, , blob, - .
, ___/BD (_= space) $2f4244 hexidecimal, , , 3097156, - blob, 64.