Sergey,
NOW I get it. Sometimes I get hit by an attack of the stupids and other times I don't need the attack. Thanks for the slap on the back of the head. I THINK I'm awake now.


>Hi Pete,
>Maybe I'm missing something but you can use fox2x tables in VFP 7 and they will stay in fox2x format as long as you don't run any foxpro commands on them that requere exclusive use of table, like PACK, INDEX, MODIFY STRUCTURE. There's also the SYS(2029) function that will tell you a table type or you can use low-level function or external program and read the first byte of the dbf file where table type is stored.
>
>>Thanks Sergey,
>>I guess I wasn't very clear in my question. The COPY TO command is what I'm trying to avoid. Just looking at a directory file doesn't tell us which table is FPW2 and which is VFP7.
>>
>>What I meant to say was that AFTER we convert to FPW2, we run dBConvert to create .DAT files. We then usually have to modify the original VFP7 files again because of some new customer requirement. That means we have to COPY TO again, and run dBConvert again to create a new .DAT. This can go on quite a number of times.
>>
>>We do a lot of this work from the command window. We will sometimes work with 10 to 15 tables to convert per project, 20 projects per week. Every COPY TO command just slows us down. We are a mailing company so very few of these jobs lend themselves to applications.
>>
>>I thought maybe the "dBase compatible" switch in the Options screens would help, but I guess that was for input only.
>>
>>Pete
>>
>>>COPY TO ... TYPE FOX2X will create a copy of the table in Fox 2.x format.
>>>
>>>>Hi all,
>>>>Seems like I have nothing but questions since starting with VFP7.
>>>>
>>>>We have to take our created tables and convert them in a third party app, dbconvert by GMC, part of PrintNet. We now have to save our VFP7 tables as FPW2.6 tables so dbconvert will recognize them. Then of course we have to modify the tables and resave as FPW2.6. We're doing this A LOT.
>>>>
>>>>Is there some sort of ADD-IN that will always save VFP7 tables as FPW2.6? Maybe something that could be called from inside a .prg so that only certain tables are affected.
>>>>
>>>>We also use PostalSoft software, which we haven't tried with VFP7 tables yet, but we're concerned that they also may need "true" dBase files.
>>>>
>>>>Pete