Thanks for the information Helen. However, by this...

> That is "as designed" (on the database engine side). The executable code for a SP is held in the database cache to protect it from changes being done whilst the version is in use. The SP recompile will be allowed once the cache is cleared. For SS, that means when the database goes offline (no connections at all, then DB Owner logs in exclusively). For CS and embedded, where each connection has its own individual cache, the cache is unloaded when the connection is detached.

...do you mean that if I use Classic Server instead of Super Server, when the user(s) who have accessed the stored procedure disconnect I can make the change rather than everyone having to disconnect? If so, I can live with that!

Cheers,

Bamber.