Thanks again Michael (and others)

My preference indeed is to skip the conditionals and the dynamics. On the other hand, the number of stored procedures would run into the 100's. I am building an ASP website, and all calls to the database are stored procedures (to make a conversion to asp.net later more simple).

On the ASP side, all customers have their own website. Every .asp file basically consists of two lines:

#include customer settings

#include common file

So, with any number of customers, there's always just one file for me to update (the common file).

Obviously I would like to have the same type of setup for the database. It would be a drag to have to update the same Stored Procedure 50 times for each of the 50 customers.

Probably the best would be is, after a Stored Procedure has been created or modified in a test enviroment, run a script that creates/modifies all the counterparts in the customer databases.

Thanks,

Raymond