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