Tom,

while what you say about the integrity of memo file data is certainly true, I just want to throw in that while it is an "exposure", it is also a FAIRLY RARE event.

For instance, a whole lot of FP, and even way more in VFP, depends on memo data and trouble is rare in the product itself. I admit there seems to be a worrisome number of .SCX trouble reports, possibly rooted in its .SCT, but its apparent confinement to that area suggests to me that it is more a particular problem rather than a generic one.

Cheers,

Jim N

>Eric,
>
>Foxpro already keeps memos in a separate table (.fpt) all that is in the record of the parent table is a pointer to the appropriate entry in the .fpt file.
>
>While this is free and works fast, it has inherent issues with integrity. Often the files get out of synch and need to be repaired with one of the third party products that are available for this purpose (dbFix for example). All they do is add another table or column, depending on the particular product, that is a second pointer in the .fpt. This makes re-initializing the links easier.
>
>HTH,
>Tom.
>
>>Does it have some impact on performance or reliability to have some memo fields in a table ? Is it better to keep them in a separate table ?
>>
>>Thanks
>>Eric