Hi Sandi.

>I have a database which used to contain some tables. I needed to free the tables as part of a series of changes to the data model. I am using SDT in my application (as part of a Visual Extend Framework). Normally when I send the new executable, I send my dbc files & my meta files (COREMETA, SDTMETA, SDTUSER, DBCXREG. When I 'practice' on a copy of my clients data (running the runtime, jsut as they do), I get an error saying it cannot link one of the newly free tables with the database, missing or duplicate fields, and it asks if I want to free the table.

You really shouldn't need to do anything different than your normal update process to handle this. Here's what I did to test this:

- Created a database and some tables in a DEV directory and created SDT meta data for it.
- Created a directory called CLIENT containing a copy the DBC and its tables (emulating a client's data directory).
- Removed a table from the DEV copy of the DBC, then added it back to SDT's meta data as a free table.
- Copied the DBC, DCX, DCT, and meta data tables to the CLIENT directory.
- Used oMeta.oSDTMgr.Update("ALL!ALL"). It changed the header of the existing copy of the freed table so it's no longer marked as belonging to the DBC.

You don't need to use REMOVE TABLE (in fact, that'll give an error) because the DBC no longer contains the removed table.

Doug