>>Is there a way to move data tables from one DBC to another, aleady-exisiting database without first freeing it (which I assume will lose all DBC-specific stuff like captions and long field names)? Long ago, I dumbly put one of application's tables into three different databases (each in a different folder) and would like to consolidate them. I've no problem hacking the database files if needed, but am not sure of everything I should look out for.
>
>>> If one of your existing tables is the right one, why not just append from >> the other two and then drop these two?
>
>Sorry, what I should have said is that I dispersed the application's tables into three different databases, not that I had duplicated any one table in more than one DBC. Other respondents reminded me of the DATABASE parameter in VFP's COPY TO command, which was what I needed. Thanks!

You may still be better off running gendbc for all the databases, then consolidating that into one big prg which will create a fourth database, then appending the data from the old ones. The reason I'd rather do it this way is that the copy to... database doesn't carry over all the extended properties - not even the defaults. Haven't tried that recently, but I remember it had shortcomings. GenDbc will give you ALL the extended properties, and it would save you a lot of time if you had a lot of them.