>>>Thanks for the response Terry, however, it turns out I didn't have a corrupt memo file.
>>>
>>>I automatically get mailed errors from the error log and this one came up and >>I thought s#!^!!! but then when I tried to open it, it was fine.
>>>
>>>Thanks anyway, I will keep your suggestion for future reference.
>>>
>>>Kev
>
>>I've seen errors where you can browse the table, but you can't select the data >with a SQL - SELECT statement. In my case, you could browse the table and have >the memo window open and it was OK. It would only crash if you tried to open >the memo window from the browse (dbl-click, CtrlPgDn).
>
>Found this old message. What do you mean by "It would only crash if you tried to open the memo window from the browse (dbl-click, CtrlPgDn)." Where are you when you do a dbl-click then a CtrlPgDn?

Just what it says. < s > You'd get the error only when you opened the memo window from the browse. You could access the data programmatically (able.memofield), but it was scrambled.

If you double click in a browse window on a memo field (or ctrl-pgdn from the keyboard), you should open a separate window for editting/viewing the memo.