>I searched for this, but didn't find enough to help, so... What is one-of-the-really-great ways (I would say best, but there may be some dissent on that) to send changes in views in the DBC to the client without having to reload all the production data? Can the DBC simply be copied into the app directory without breaking the links to the data? Do I need to recompile and send a new EXE also? What other considerations are there? Thanks!
>
>Regards, Renoir

By "without breaking the links to the data" I assume you have table's associated with the database.

If the only changes made to the database (DBC) are to views and not to data structures, then you can copy the DBC files (DBC|DCT|DCX) only. The table links will be fine.

The only reason for rebuilding the EXE would be if there are changes in the views that would cause errors (e.g., a field removed from a view that had been used in code).

Another option is to create a small update EXE that runs view creation code against the existing database on the client side.
Here, you have to be careful that the database you use in-house to update the views has the same structures as the client data you'll be updating. Otherwise, you'll get "Base table structures have changed..." errors.

Or get SDT (<- follow the link).