>
>For me, REINDEX has the advantage over INDEX ON that I don't have to re-set the relations in the database container. In an event of CDX header corruption, (which IMO opinion is less frequent than in FOX 2.x times) your can take a copy of an empty CDX file, place it over the corrupt one and then reindex.
>

I normally only use a DBC for views, so I don't have any persistent relations. In cases when I have used a DBC for permanent tables, I've relied on SDT for my reindexing just because of issues like this.

Your solution of shipping an empty CDX is good. It doesn't quite fit with the way I've become accustomed to doing things because I don't normally like to ship data or indexes with my app--they're built when you start the app.