Hi Matthew.

>Is there any reason, why you can not send a new .dbc to someone? Let's say I add a table to my .dbc. If I send the updated .dbc with the new table does that work the same as your suggestion of Open Database, Add Table?

This won't work for several reasons:

- If you change the structure of a table (eg add a new field) and ship the DBC to the client, they won't be able to open their copy of the table any more because the DBC and DBF don't match.

- If you create a new table and ship the DBC to the client, you can't use CREATE TABLE to physically create the DBF because it's already defined in the DBC.

Bob Archer mentioned Stonefield Database Toolkit (SDT). SDT makes this a completely generic, transparent process:

- include our class libraries in your project (they're royalty free)
- ship the new DBC to the client along with some meta data tableds created and maintained by SDT
- instantiate one of our classes
- call the Update() method to create new tables or update the structures of existing ones

This is *way* easier than scripting the CREATE TABLE, ALTER TABLE, CREATE SQL VIEW, INDEX ON etc. commands you'd need to do if you did this manually. Plus, SDT provides table and memo header repair and corrupted index repair functionality, *plus* provides developer utilities like automatically fixing broken views when you change the structure of the underlying tables.

SDT is available for a discount for UT members. Check out www.stonefield.com for more information and a demo you can download.

Doug