Contaminated DBT Memo file 3

[wildcard]

Memo records in a .DBT file are not linked correctly
to their original parent record. There appears to be
no obvious pattern to the contamination, but rather a
random misfit.

1. How can this happen?
2. How can I repair the problem?
3. How can I prevent it happening again?

EXE compiled with Clipper 5.2b and linked with TLINK.

 

[circes9]

yep, sorry to report that dbt free block pointer's files are fragile and can get corrupt.
I use a utility program named Dsalvage that, among other things, will usually fix dbt's.
Good luck

 

[GAstrada]

Wildcard: dbf's and dbt's were always fragile. I've used to make at a times a "copy to xx".
Then, when I've renamed the "xx" to it's original names, I've found : correct correlation between files, and, moreover: dramaticall reduction of the size of .dbt file. It seems that the .dbt files doesn't support correctly pack, zap, edit and others workaround tasks.
regards. Gustavo.

 

[wildcard]

Perhaps we should all adopt a minimum standard when
handling .DBT files and stop using suspect commands:-

Rather than using the 'PACK' command, maybe we should...
USE original EXCLUSIVE
COPY TO tempfile for .NOT. DELETED() and then
ERASE the source database and source .DBT file and then
RENAME tempfile.dbf to original.dbf and also
RENAME tempfile.dbt to original.dbt then
USE original EXCLUSIVE
ERASE (all relevant index files) then
INDEX ON [field list] TO indexfile

Also rather than use the 'ZAP' command, maybe we should...
USE original EXCLUSIVE
COPY STRU TO tempfile
ERASE original.dbf
ERASE original.dbt
RENAME tempfile.dbf TO original.dbf
RENAME tempfile.dbt TO original.dbt
ERASE (all relevant index files) then
USE original EXCLUSIVE
INDEX ON [field list] TO indexfile

What do you think, guys?
Jim

 

[GAstrada]

I agree with you. Moreover: standardized methods will help us to make more reliable apps, and definetely gain the battle with the "garbage" that .dbt files like to accumulate, which, at last only run out of space our drives, and make apps unstables, or not reliables. Not CA, nor third party software house seems to solve the bugs.
Regards.