>>But SDT doesn't recover for you ALL the things in a DBC.
>
>Such as? It's possible that you're correct; I haven't had to send out a .DBC with an app that I've developed since I started using the product; instead, I simply send out updated .DBC metadata and let SDT at the customer site do all the work. I've updated tables, views, indexes, stored procedures including default and non-default RI using it. Connections are built on-site, simply because I don't have the deployment details back at my office, but they're done by creating records that I merge into the metadata at the customer site. And with 5.1, it also handles many of the details of free tables and the like.

Hum? Don't know exactly what SDT is doing from inside, but from days age I've been looking at the DBCX2 model, and there is no data nor fields, for things like the field caption, ri, stored procedures... if SDT uses only dbcxreg and coremeta there is not such data, if it works for you maybe SDT extracts this stuff from the DBC, and trusts in some DBC data (not me! if the DBC would be corrupted)

Sorry, I only have the demo version and can't test this.