>We are having a lot of problems with not only getting corrupt memo files but missing memo information from certain records as well. I know that there is not a whole lot that we can do about the corrupt memo files other then to increase the stability of our infrastructure.
>
>Our larger problem however, is that users are reporting that there is missing information from fields that they cannot edit and that should never be cleared out. The worst part is that many times we are not aware of the problem until even months after the the field was cleared and therefore troubleshooting is out and restoration is a nightmare.
>
>I know that there can be isses with memo pointers becoming screwed up, which I suspect is happening, but is there anything we can do to minimize our risks? Does anyone else have problems like this occuring?
>
>Since we are mainly concerned with one field, we were thinking of including a logical field in the table that would indicate whether there should be data in the field or not. With this we could run a nightly process to let us know if there is data missing by checking to see if the field's is empty against the contents of the logical field. Does anyone have a better idea than this?
>
>Thanks for your help,
>
>Jason

If someone has access to restoring the files, make sure they are restoring both the DBF and FPT.
Just a thought,
Tracy