Terry,

Sorry, if I wasn't clear. My explanation below was releted to UNION only. UNION ALL allows duplicate records to be present in the result set.

>Hi Sergey,
>
>Thanks. Apparently I misread your previous message when you said "In VFP8 you cannot include Memo/General fields in UNION select even with other fields." I took that to mean that even with a UNION ALL, you could not merge two tables when they contained memo fields. If you can merge tables with memo fields in VFP 8 with UNION ALL, everything will be OK.
>
>Thanks,
>
>TFISHER
>
>>The same way as in VFP7, with UNION ALL.
>>
>>>Sergey,
>>>
>>>How would I accomplish this table merge in VFP8? I don't want to write something now that will break in a few months when VFP8 comes out.
>>>
>>>Thanks,
>>>
>>>TFISHER
>>>
>>>>>Your error from the Union of the two memo fields most likely is due to different Memo Blocksizes for the two tables. If you get a chance, would you check this theory. Thanks.
>>>>
>>>>Nope. The error is generated because UNION requires VFP to do DISTINCT on the records in the result set but VFP doesn't compare MEMO/GENERAL fields in DISTINCT operation and there are no other fields to compare. In VFP8 you cannot include Memo/General fields in UNION select even with other fields.