>Mark,
>Thanks for the reply. I take it from what you said that the DBC is NEVER updated from CoreMeta and that to update a user site I must (each time I change the data structure) sent all 13 of the files you mentioned. Have you ever had an occasion when any of these have happened 1. User copied an old version of the table into the production directory, 2. The DBC dropped several index tags from a table 3. Any other situation where the DBC, the actual tables and or CoreMeta did not agree about the true data structure. I am trying to get a handle on how to quickly fix the data messes that Happen.

Here is where your users need some formal education -- NEVER, EVER just copy 1 old table back to your data directory unless you know dang well it is still synchronized with all the other tables in the DB.

You are responsible for assuring the 13 files are all in synch with each other when you send them. If the user has copied an old version of a table back to the data directory, the UPDATE will fix it [with potential data loss] after you send the 13 files again.

The only time I lost indexes was when my DBC was not in synch with my SDT meta data. This would likely happen by sending an old SDT meta data version with the updated DBC/DCT/DCX files.

To assure you are in synch, open the SDT Explorer and validate all the meta data [one of the buttons on the right end of the SDT Explorer toolbar].