>>>>I'd start by taking a look at the CREATE TABLE command. Rather than copying out an empty table, you can build it in place. The following line of code would create an empty table called MyTable with three fields, a 25 character character field MyFirstFld, a numeric My2ndFld and a memo field MyMemoFld:
>>>>
>>>> CREATE TABLE MyTable (MyFirstFld C(25), My2ndFld N(8,2), MyMemoFld M)
>>>>
>>>>No need to have a physical copy of the .DBF and .FPT - just build them as needed, where needed.
>>>>
>>>>This doesn't solve the problem of starting with a non-empty table.
>>>
>>>These one's are all empty to start with, so that would work.
>>>
>>>Thanks,
>>
>>Michelle,
>>One problem with CREATE TABLE is that if you ever need to change the structure, you will need to dig out the code - that's why I choose the empty dbf route - only my personal preference.
>
>My experience is that if a table's structure is changed, the code has to be revisited in any case.
>
>Ed

Good point!