Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Problems with Memo fields and .DBF/.DBT
- Thread starter yunta
- Start date
hemantpandya
Programmer
Hi
What is the size of your DBF/DBT file.
Is any curruption previously and repaired.
Pls inform
What is the size of your DBF/DBT file.
Is any curruption previously and repaired.
Pls inform
- Thread starter
- #3
[ Yunta ]
It looks like you may have exceeded the maximum file size for a conventional DBT file. I think it is about 17mb and your DBT file is almost twice that size. Refer to your Clipper documentation or the NG for the exact maximum file size. I had this happen to me many years ago and the most simple solution I found was to change file formats. I changed the RDD to CDX/FPT and wrote a small conversion program to copy the records/text from the NTX/DBT to the CDX/FPT. Some of the more corrupt entries I had to recover with a standard word processor. Other possibilities are the super memo driver with Clipper 5.3b, or even individual text files to replace the memo file.
Perhaps there are other solutions, but as I see it this is a serious problem that should have been addressed when it failed the first or second time.
Sorry for the bad news, maybe someone else has solved this in a more simple way.
Regards,
David Tracy.
It looks like you may have exceeded the maximum file size for a conventional DBT file. I think it is about 17mb and your DBT file is almost twice that size. Refer to your Clipper documentation or the NG for the exact maximum file size. I had this happen to me many years ago and the most simple solution I found was to change file formats. I changed the RDD to CDX/FPT and wrote a small conversion program to copy the records/text from the NTX/DBT to the CDX/FPT. Some of the more corrupt entries I had to recover with a standard word processor. Other possibilities are the super memo driver with Clipper 5.3b, or even individual text files to replace the memo file.
Perhaps there are other solutions, but as I see it this is a serious problem that should have been addressed when it failed the first or second time.
Sorry for the bad news, maybe someone else has solved this in a more simple way.
Regards,
David Tracy.
- Thread starter
- #5
Yunta,
The size limit for a DBT file is 32MB, which means that the file becomes highly unstable once it exceeds that size. There are a number of things that can be done to correct this. The first is to pack the DBF (best done by a copy for .not. deleted() to a new file). An excellent (and free) tool for further compressing the DBT is a small DOS program called DBTCHECK, which you should be able to find on the Web. Neither of these procedures will necessarily fix the corruption, but may. Nevertheless, once the corruption has been cleaned up, these two procedures should save you from further problems of this kind.
PS--If neither of these shrink the DBT enough, you'll need to archive some records to reduce the DBF further, which will also shrink the size of the DBT.
The size limit for a DBT file is 32MB, which means that the file becomes highly unstable once it exceeds that size. There are a number of things that can be done to correct this. The first is to pack the DBF (best done by a copy for .not. deleted() to a new file). An excellent (and free) tool for further compressing the DBT is a small DOS program called DBTCHECK, which you should be able to find on the Web. Neither of these procedures will necessarily fix the corruption, but may. Nevertheless, once the corruption has been cleaned up, these two procedures should save you from further problems of this kind.
PS--If neither of these shrink the DBT enough, you'll need to archive some records to reduce the DBF further, which will also shrink the size of the DBT.
Yunta,
The size limit for a DBT file is 32MB, which means that the file becomes highly unstable once it exceeds that size. There are a number of things that can be done to correct this. The first is to pack the DBF (best done by a copy for .not. deleted() to a new file). An excellent (and free) tool for further compressing the DBT is a small DOS program called DBTCHECK, which you should be able to find on the Web. Neither of these procedures will necessarily fix the corruption, but may. Nevertheless, once the corruption has been cleaned up, periodically using these two procedures should save you from further problems of this kind.
PS--If neither of these shrink the DBT enough, you'll need to archive some records to reduce the DBF further, which will also shrink the size of the DBT.
The size limit for a DBT file is 32MB, which means that the file becomes highly unstable once it exceeds that size. There are a number of things that can be done to correct this. The first is to pack the DBF (best done by a copy for .not. deleted() to a new file). An excellent (and free) tool for further compressing the DBT is a small DOS program called DBTCHECK, which you should be able to find on the Web. Neither of these procedures will necessarily fix the corruption, but may. Nevertheless, once the corruption has been cleaned up, periodically using these two procedures should save you from further problems of this kind.
PS--If neither of these shrink the DBT enough, you'll need to archive some records to reduce the DBF further, which will also shrink the size of the DBT.
- Thread starter
- #8
- Status
Similar threads
- Locked
- Question
- Locked
- Helpful tip
- Locked
- Question
- Locked
- Question