>See CREATE FROM in Hacker's Guide. I have not read it yet...
>

He-he.

CREATE FROM doesn't ignore deleted records in the structure table. This means if you COPY STRUCTURE EXTENDED, then modify the table by deleting some of the records (that is, remove fields from the listing), you need to PACK the structure table before issuing CREATE FROM. Otherwise, your new table will have the fields you tried to remove. This bug is nothing new—older versions do the same thing.


Given the various problems and peculiarities of these commands and the fact that there are better ways to do everything they do, we recommend you stay away from these.



>>Hi Steve,
>>
>>The strange thing is, what this code was working correctly for more than a year. Only today I found this strange thing. Does your other suggestion with copy to command properly copy all things (field rules/table rules)?
>>
>>>Nadya,
>>>
>>>No problem...I'm eating lunch anyway.
>>>
>>>I can't find it documented in VFP help or in Hacker's Guide. Also, I haven't figured out how it handles the DATABASE keyword. If I leave that keyword out, it will prompt me to overwrite an existing file. If I leave it in, I get an error on the second attempt at creating the same file name. However, the new table does not appear to be actually added to the DBC.
>>>
>>>You could go with my other solution (the COPY TO command), or take out the DATABASE keyword. Then add the new table to the DBC (if it is not there).
>>>
>>>>>Oops...I didn't notice that you weren't using CREATE TABLE.
>>>>>
>>>>>CREATE gives an error of the table you are trying to create already exists in a database...
>>>>
>>>>Hi Steve,
>>>>
>>>>Sorry for bothering you again. Where did you find the description of this command in Help? I just can not. CREATE command Help doesn't show DATABASE keyword, etc.
>>>>