Arthur

I hope that VFP7 does automatically fix memo fields, but something tells me that if it did, there would have been a large mention of it. To me, corruption of memo fields is the BIGGEST problem I've got with Foxpro and if that was fixed I would never slate the product again!

Kev

>I received a C0000005 crash during a SQL Select. Searching on the Internet located a Spanish-language posting that seemed to indicate memo field corruption. I browsed the source table and found that the memo fields were indicating contents (the word "Memo" was in upper case instead of "memo" indicating no contents) when opening the memo field on that same particular record showed no contents. I reopened the table exclusively and performed a pack and it blew up. I saw the old "memo field is missing or invalid" error. Out of sheer stubbornness, I tried to open the table, and -- lo and behold -- the browse window indicated the proper memo field contents.
>
>In my own long-winded way of going around the moon to get to the house next-door, I am wondering if Foxpro 7 fixed the memo field. It never used to do this of course, so we used to have to buy software from somewhere to fix this, but I installed this computer so I know it has no other utilities for fixing problems of this nature.
>
>Does VFP 7 finally have the ability to fix it's memo files when they become damaged?
>
>Art
>http://members.aol.com/ARTGR/