Map Question

• create copy of your "source" table at Access (inside MDB)
• add new columns… fill the content… (database operations)
• register that "new" table at BM - Settings, Database, Setup, Table - Add to MSCatalog
  • (new table will have new entity number)

• go to Tools, Database, Open Verify Linkage - icon Review Elements by File, select all rows, set On - Entity at right corner, fill new entity number
• icon Process Selected Rows
• elements will be "redirected" to new table now

Miro

What you are doing is creating ‘n’ new features, as far as the database is concerned. You could approach this through the GSA or manually edit the xml file and refresh in the GSA.

All GSA
1. Create the tables in the database.
2. Remove the properties of the existing feature that are now represented by the new tables.
3. Refresh the database connection, getting the new tables.
4. Add the properties from the new table to the existing feature(s).
5. Update the SQL statements.
6. Update the placement metadata.
7. Export the workspace(s).

Edit the XML file directly. ( I am assuming the existing column names will not change when going to the new table)

1. Create the tables in the database.
2. Change the name of the table in the XML file for the feature.
3. Open the GSA.
4. Refresh the database connection.
5. Add the new properties from the new table to the existing feature(s).
6. Update the SQL statements.
7. Update the placement metadata.
8. Export the workspace(s).

The second method may seem like more steps, but step 2 allows you to just change the table name and not have to remove and reinsert the properties for the features, which can be tedious.

Either method, please make a backup copy of the XML file before editing.

Thanks Jerry.
Sebastien...... thanks and I agree we also would prefer not to directly edit the .XML file but we don't seem to have a choice in some rather basic cases. As an example, in Command Manager, how would you sort the Feature Names alphabetically? For years we've had to do this by a manual edit of the .XML file because a 'sort' option wasn't available. I certainly take your point of potential dangers though.