Memo file ..... is missing or is invalid

[medic]

This error message is displayed after I issued a PACK command on my open table with index and memo file. <br><br>The error is not displayed when opening the table, neither when editing the associated memo field nor when adding a new record. <br><br>I tried overwriting the memo file from a working backup copy but it did not solve the problem.<br><br>Can anybody help me fix this?

 

[dgrewe]

Since You have already overwriten the memo file from a backup without overwritting the DBF and CDX at the same time, you have effectively stopped any way of recovering the data from the memo file.&nbsp;&nbsp;If you ever do manage to get it open, The record pointers in the DBF and CDX will be printing to the wrong place in the memo file.<br><br>Your only hope now is to reinstall a backup copy of the DBF, CDX and FPT that existed before the Pack command and start from there.<br> <p>David W. Grewe<br><a href=mailtoave@internationalbid.net>Dave@internationalbid.net</a><br><a href= > </a><br>

 

[CDavis]

DSALVAGE PROFESSIONAL is a software package that might help -- I suspect you would have to do some manual manipulation of pointers etc.&nbsp;&nbsp;I don't know for sure, I've never had your particular problem.<br>--cd.<br><br>

 

[medic]

Thanks for the response guys! <br>Sometimes we really overlook simple solutions to problems.<br>In this case for example, I failed to realize that my database<br>can be fixed by creating a new table with the same structure. Then appending all records from the table with the &quot;partially&quot; corrupted memo file since I can open the table and the contents of the memo field is still accessible.<br>Thanks for those valuable info Dave. Whew! :-D

 

[dgrewe]

Perform This Check.<br>Place the database in natural order (no indexes or orders)<br>Go to the bottom of the database.<br>Look at the last entries in the memo field and make sure they are for that record.<br><br><br> <p>David W. Grewe<br><a href=mailtoave@internationalbid.net>Dave@internationalbid.net</a><br><a href= > </a><br>

 

[medic]

Yes Dave. I checked those records and they're correct.<br>I'm just wondering, what was that particular &quot;error&quot; in the memo file which caused FoxPro to disallow the PACK command on the memo file considering that it permits access and update to the associated table specially its memo field (its data is correct based on the selective record check I did).<br>What do you think Dave?

 

[dgrewe]

The last time I saw that error is when a network User (abuser) had the memo file open with a word processor look at it to see what it was and left it open when (she) when to lunch. <p>David W. Grewe<br><a href=mailtoave@internationalbid.net>Dave@internationalbid.net</a><br><a href= > </a><br>

 

[Guest_imported]

If the file still exist, but just isn't usable.&nbsp;&nbsp;Then, it's been corrupted for whatever reason.&nbsp;&nbsp;I have this happen to me when a user shuts down the computer w/o properly exiting and at the time, I have an active memo file up.

It's not straight forward.&nbsp;&nbsp;But, I've always been able to repair it because VFP has a repair capability built in.

The problem is that it always takes me a while to get to work.

You have to delete the data table from the DBC first and make it an independent table.&nbsp;&nbsp;Then, if you try to do a use exclusive on it, it will tell you the memo file is bad and if you want to repair it.

Then, add it back into the DBC.&nbsp;&nbsp;However, if you had any long fieldnames in the DBF, you have to rename then since they're lost when you separate the table from the DBC.
That's why I use standard 10 char or less names.&nbsp;&nbsp;So, if I separate and re-add a table, I don't have to deal with the loss of long field names.

 

[ccheney]

I am having the same problem with a Visual Foxpro table.&nbsp;&nbsp;Some of the memo fields are corrupt.&nbsp;&nbsp;When you access the table, it is ok.&nbsp;&nbsp;When you reach certain records you get a fatal exception error (C000005), which I know is because the memo field is corrupt (data from all other records in memo).&nbsp;&nbsp;Other than creating a new table and appending all but the memo fields into the new table, is there anything I can do?&nbsp;&nbsp;I have tried DSALVAGE PROFESSIONAL, but it does not work with Visual FoxPro.&nbsp;&nbsp;Any ideas or suggestions would be greatly appreciated.<br><br>Thank you!

 

[khoona]

Not to plug any commercial product, but most developers I know who use *any* product to fix files use Stonefield Database Toolkit.&nbsp;&nbsp;It creates and maintains an &quot;extended&quot; data dictionary with all the info to repair and/or recreate the table header, which is frequently corrupted, rebuild indexes from scratch, and in some cases, repair memo corruption.&nbsp;&nbsp;The product's roots go back to FoxPro 2.0 for DOS, and has no real competitors in the marketplace.&nbsp;&nbsp;Go to <A HREF="

http://www.stonefield.com"

TARGET="_new">

http://www.stonefield.com</A>

for more info.&nbsp;&nbsp;I am a friend of the author, but it's STILL the best tool out there.

 

[ccheney]

FYI:&nbsp;&nbsp;I exported the table to version 2.X and ran DSALVAGE PROFESSIONAL on the tabel, which found no errors.&nbsp;&nbsp;I imported the table back into Visual and have no errors in it.<br><br>