How save are memo fields

[mkendi]

Because I am anxious of losing all of my data in case of a dammaged memo-table, I tend to store my information in char-fields. I know: not very clever.
I my current application the information to be stored is very various, so a char-field solution is not possible.
So may I ask you:
1. How secure are memo-tables?
2. In case of a damage, are there tools available to restore the data?

Thanks in advance

 

[mkendi]

Sorry, should be "safe" and not "save".

 

[DSummZZZ]

Memo fields are not very safe. I try avoid them. But of course, they are unavoidable at times.
They are really about as safe as an index file. An interuption in processing will trash them just as fast as it will an index file, especially if you're in the middle up a file update/write.
That said, there are tools to repair damaged memo files. Do a keyword search in this forum, and you'll find some of them.


-Dave S.-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[pasu]

I have experience on a 200000 records FoxPro table (with memo field) with around 100 users. The memo field lost the 'link' with the table almost once every 2 months. Example: The memo fields use to belong to records 100 will become belonging to record 101! Sometime, the memo field will be chopped into two records, part of it in record 100 and part of it in record 101!

My solution for that is use a seprate table only for the memo field and the key. It reduces the chance for coruption, and the bottom line is...do a lot of back up.

 

[mkendi]

Thanks for your advices. I will continue to stay away from memo-fields!