>In VFP6, if there was a corrupt memo file it would give you the option to repair the table. In VFP9 it will not open the table. How are you suppose to repair a corrupt memo file in VFP9?
>
>Brenda

You may be experiencing a BIG GOTCHA here.

I recently went through a hell similar to this during the upgrading of a VFP7 app to VFP9. I modified some of my table structures to change some character data types to varchar. Later on, I was working on some SQL where I needed to set the ENGINEBEHAVIOR back to 70. TO my "surprise", I kept getting a "feature not available" error on SQL that had worked perfectly before. What a totally useless message that was, but in hind sight the message was technically correct just not usefull in finding the problem. In the process of trying to figure out what the problem was, I corrupted the memo files of these tables. I found out too late that by setting the ENGINEBEHAVIOR back to 90 allowed me to open the tables, but all the data in them were beyond recovery, and I still could not access the memo fields. Thankfully, I had a backup and this was only test data.