Hi Sandi.

> My question is what do I do with the COREMETA, SDTMETA, etc.?

You have several choices:

- Include all DBCs in a single set of meta data tables. I don't recommend this because some applications will then have meta data for DBCs they don't use. That means you can't use something like Update("ALL!ALL") because it would try to update or create tables it shouldn't.

- Have a separate set of meta data for each DBC. This is kind of a pain, because each DBCXMgr object can only work with one set of meta data at a time. You'd have to instantiate several instances of DBCXMgr in your app, one for each DBC.

- Have a separate set of meta data for each DBC but programmatically combine them for a given application. For example, you might have set 1 for DBC1, set 2 for DBC2, etc. For APP1, which uses DBC1 and DBC2, you'd combine set 1 and set 2 into a set just for APP1. For APP2, which uses DBC1 and DBC3, you'd combine set 1 and set 3 into a set just for APP2. Combining meta data tables is easy, using code similar to the following:

use DBC1\COREMETA
copy to APP1\DATA\COREMETA with cdx
use APP1\DATA\COREMETA
append from DBC2\COREMETA
*same thing for SDTMETA

The thing to remember in this case is never let SDT validate a DBC into an app-specific set of meta data, only into the "master" copies (eg. in DBC1\ and DBC2\ in my example above).

Doug