I have done what your attempting and it works fine if you verify something first. You can drop in a new Database as long as your tables haven't really changed. And by that, I mean, your table structures. For example, I have made changes to Views, Captions, Default values and other related items that are stored in the Database. Then, I dropped in the new database in the production area and all works fine. The problem really happens when you make changes to the table structures because you will then get some pretty serious errors in multiple places where those tables are opened or accessed.

Any time that I've needed to make structure changes, I've had to write a program to update the production tables thru my code. This can be very time consuming, but can be done.

Hope this helps.

>I need to update the stored procedure in a live version of a DBC. How can this be done with the least likelihood of killing the database?
>
>I was thinking (for lack of experience) that I could overwrite the DBC, DCX, and DCT files with the new versions. This doesn't sound safe. Is there a better way?