Hmm,

Views aren't an option (unless I'm missing something obvious) because VFP simply won't read the tables with too-many fields. If the Clipper program can be changed to use 'Fox2.x' compatible tables (maybe splitting long tables into one-to-one linked tables) then your VFP program would read/write. You'll also have to go to CDX indexes in the Clipper program (same driver as the FPT change, but I forgot to mention it). If it's a Clipper 5.x program, the driver that changes index and memo structures is included.

Unfortunately, a LOT of the change will have to be made at the Clipper end.

Barbara

>Barbara,
>
>Thanks for the quick reply.
>
>>Steve,
>>Do you have the original Clipper source code? If so, you should be able to recompile it with so it uses FPT rather than DBT memo fields. Unfortunately the other problems (too many fields, fields too long) are NOT addressable so easily. You will have to make some changes there.
>
>Yes, the clipper developer is on staff at the company where the project is in use. I'll need to ask him about the memo field format.
>
>>
>>Are the two programs going to be run simultaneously? If not, you might write a Clipper program that runs in the background and updates the tables used by VFP, splitting the longer tables and reducing field size where appropriate.
>
>Unfortunately, yes, both app will have tpo run simultaneously. That is why i am thinking Views, which couild allow me to split tables, keep memo fields comptible, and ignore the clipper indices. Can you comment on that approach?
>
>>
>>HTH
>>Barbara