Hi Sandi.

>Hi. I'm using Version 2.6. I have a base product with about 100 tables. I customize my product for clients and sometimes I need to do a more major customization which includes some additional database tables. I don't really want to clone the whole thing and keep a complete data dictionary for the customized version, because if I need to enhance the base product I don't want to be forced to 'fix' more than one data dictionary set as the table enhanced would be in more than one dictionary - say the customer table.

There are several things you could do. One is to keep the custom information in a subset of data dictionary files. IOW, the "master" set keeps the common stuff and for each client you do customization for, have a set that only contains the custom records. Then, before you ship to the client, you combine the master and custom sets into one set you ship them.

An easier approach might be to have a separate set of data dictionary files for each client, and create a utility program that goes through each custom set and updates it with any differences in the master set.

>Second question - Is there a way to use AUTOKEY to provide more than one automatically generated field (numeric incremented) for the same database table?

Yes, but you'll need to change the logic in AUTOKEY a fair bit. You'd need to pass a second parameter (the field to be assigned the value), add a column for the field in SYSDATA.DBF, and make AUTOKEY look for both the specified table and field.

Doug