>>Let me rephrase this question.
>>I want to use a table already part of the DBC as a
>>template to create monthly files on the fly. I can
>>do this, but I have not been able to maintain long
>>field names or any other useful DBC properties. Any
>>information regarding this would be greatly appreciated.
>
>I've tried this, and got the long names carried over - maybe
>saving/copying the RI and other stuff may nead some more work:
>
>Open data the_dbc
>use first_table
>=AFields(stru_la)
>stru_la(1,12)="Second table's long name"
>create table second_table from array stru_la
>
>The trick was to change the table's long name, otherwise it collides
>with a long name already in the .dbc, and it doesn't get registered
>there. Well, whatever properties get saved via AFields() will get
>transported - you'll have to manage with the others.


Great. Thanks for the info. Will try.