>>Doesn't GenDBC require exclusive access?
>
>AFAIK it only creates an empty shell, not a copy of the database.

Both true. But there are only a couple of changes needed to make GenDBC work an an open database. After all this requirement just results out of the COMPILE DATABASE statement within GenDBC, which is bad design in itself, as you would not want to touch the original database even if it's objectcode was out of sync with it's source code. That is a task of validate database, perhaps, not of GenDBC.

Still you only get empty tables, but instead of a copy you get freshly created files which most probably have no corruption in them. Appending the data to them is much slower than copying dbf/cdx/fpt, as you would rerun all insert triggers and add records one by one to the indexes. But you could simply erase all table files and have just a fresh version of the dbc/dct/dcx if that is your main intention.

Bye, Olaf.