Hi Vince.

>So what you are saying is that DBC errors are not thrown if field definitions and indices do not match, only the field names. How about the order of the fields? I had a problem yesterday where I added fields to a table, then copied the DBC files which already reflected the added fields, however, the fields that I added to the table were not in the same order as indicated in the dbc. It did not throw an error, however, the table was totaly trashed. The field names no longer matched their respective definitions nor the data. For instance, "qty" was defined with as MEMO, and "description" was defined as numeric.
>
>In short, I assume order is essential??

Order is essential as is the number of fields (ie. you can't have four fields in the physical DBF but three or five in the DBC).

Doug