We have been running Visual FoxPro for many years now. Other than making sure we do not hit the 2GB limit on the FTP, memo things seemed to run well. Recently we started getting some corruption, then we added some code which does more writing to the memo fields and the corruption has gotten horrible now. We basically created a separate table we write to as well as a backup and sometimes even that gets corrupted just so we can avoid loosing notes. The backup one will sometimes tell the user it is corrupt and we can not even use the table even shared for about 5 to 10 min then it somehow releases and everything is fine then, but we get a few blanks records in a row with nothing in them while the corrupt message occurs. Our main notepad file gets corrupted on certain records preventing it from being able to be packed, and also show the corrupt message browsing the table if you hover over the field's memo reference on certain records. We are forced to find a main notepad that is packable and run a utility to add separate entries from the backup file back into the main, but this involves kicking everyone out of the application while we do this. Any advice on how we can make these memo fields not get corrupted all the time, or an indication on what may be causing them?

Thanks in Advance


Kevin Hickman