Iain,

I think "the telltale" is simply telling you that there *IS* data present when it lists as "Memo", and means nothing as regards modification of content.

Were your most recent changes in *ANY* way related to the memo field - its editing, storage, presentation, etc. Do dates have *any* impact on th eprocessing of these memo fields?

Have you restored from *ANY* backups recently? (like, say around 11/19 or 11/18???) Possibly you restored a DBF but forgot its memo file? Or maybe you only restored a memo file, forgetting to restore also the DBF???

I s'pose it could be lots of things. Maybe, with a bit more info, someone can get to the bottom of things here.

good luck,
Jim N

>I'm on the hunt for some memo fields my users' claim are coming up emtpy after the long weekend. I created a call-logging application where the user records general call notes into a memo field which is linked to the call data via unique keys.
>
>Today, when they pulled the app up, all of the notes (memo fields) associated with calls from 11/19 through 11/25 appear to have been blanked out. When I go into the development side, there is no change. It does not appear as though the tables have become corrupt, as other memo fields appear to be intact and no fields have garbage in them. Also, the fields that are now blank show the telltale "Memo" instead of just "memo" which would indicate they had not been modified yet.
>
>There are about 8200 records in this table, could there be a physical limit to the size of the table containing memo fields? If someone could help me crack this case I would be most appreciative. I have no reason to doubt my user's (at least that I am aware of...) and would really like to know why these fields just became blank all of the sudden.
>
>Thanks in advance.
>Iain MacNeill
>Action Data MIS Department
>iain@add.com