Error in memo item 1

[Guest_imported]

Hi

We´ve lost the link between memo file(.dbt) and its xxxxx.dbf file.

Is there anyone who have a solution ?


Thanks in advance

email addr: jgg@csub.scs.es

 

[GEMS]

dear csub,
We'll assume this is error 41 - dBASE cannot open the database because it can't find the .DBT file or considers the file to be corrupt. If the .DBT is there, rename it because it may be possible to save its contents at a later date. The following procedure merely gains you access to all the data in the table except that held in the memo fields. A quick fix but maybe that's all you need!?!
1 Create a file RESTORE.DBF.
2 Give it one memo field.
3 Close the file without creating any records.
4 You should now have two files RESTORE.DBF and RESTORE.DBT Rename RESTORE.DBT to the filename that has been lost/ corrupted. Make sure this .DBT file is in the right location ie the same directory as its parent .DBF file.
(dBASE only ties the database file to the memo file by name and location- nothing more elaborate than that.)
5 Open the filename you require. The number of records will be valid and you will be able to access them all. Of course the memo fields will be blank.
Quick Fix over
If you really need the data from the .DBT files, there were some dBASEIII+ utilty programs and clipper style routines that were available to recover memo files. Does anyone know where a download could be obtained for such a facility? I'll keep looking
Hope this helps GEMS

 

[MiggyD]

Good Tip GEMS! And here's a TM tip for you.

-MiggyD

PS. Got you're email. I'll try to help reducing the extended help section between classes.

 

[GEMS]

Dear Csub Quick Fix No 2
Actually this should be Quick Fix No 1 as it ought to be the first action in these circumstances. Whenever you modify the structure of a database file, dBASE makes a backup copy of the main data file for safety reasons. If the database has a memo field, it also makes a backup copy of the database memo file. For example, MAINDATA.DBF begets MAINDATA.BAK and MAINDATA.DBT begets MAINDATA.TBK. The date stamp on these files is obviously the date you modified the structure. (Subsequent structure modifications simply overwrite these BAK & TBK files as dBASE nevers gets around to deleting the back-ups.)
So fingers crossed csub, hope someone modified the structure recently and start looking for a TBK file of the name you seek. Of course the data will be “dated” by the date stamp on the TBK file but this is often better than nothing. GEMS
Thanks MiggyD for your vote and your efforts re error codes.