llRetVal = oMeta.oSDTMgr.REINDEX('', .F., .T.)

This allows them to select which tables to reindex instead of all-or-nothing.

>Periodically, i am finding that some users are losing primary index tags on some tables. Other tags are still in place. I believe its attributable to record corruption. Two or more records get trashed and their PK fields end up having the same value. The REINDEX routine is run (without deleting the trashed records) and the primary index cannot be added back cuz of the duplicate (trashed) PKs. And i assume that the DBC's index info on this table now excludes the primary index cuz it did not get added back.
>
>I had been calling reindex using the following syntax:
>
>

>REINDEX('ALL',.t.)    && all tables, pack 'em
>

>instead of
>

>REINDEX('ALL',.t.,.t.)  && all tables, pack, use meta file
>

>
>After breaking down and reading the docs, i see that the 3rd parameter tells the reindexing process to use the META files as opposed to the DBC.
>
>Am curious about how people are calling the REINDEX option. Are u using the meta files option? Any issues w/ that method (other than having outdated meta files)?
>
>---------------------