>I have a stored procedure in a production database. What's the best way to change this without causing the
>users grief?

Welllll. If you were using a loader/launcher you could have the DBC on the users' PCs along with the exe. This gives the best possible performance, prevents DBC contention (especially with views) and means you can update the DBC on the server anytime you want. Win-win all around. No grief. The users will get the updates the next time they log in.