Thanks for the reply and the ideas. Unfortunately, we have limitations in many areas that I didn't include, but that your response has revealed.
-- We support SQL Server versions from 2005 on.
-- We do not specify what other software or options our customers must have, or have installed.
-- Most importantly: many of our customers have little or no skilled staff to even run these object creation scripts; in fact, in our original release a while ago, we only had 4 code objects, and we got a large number of calls with questions like:
?? What does the N mean before the database name, and do we need to keep it?
?? I keep getting a message that says "Don't create these objects in the master database"..what is that?
?? What's a view?
?? I get a message that says I don't have permissions to create the objects... can you give me permission?
etc.
Now you see why I need to keep this as simple as reasonably possible.
Another thought I had after reading your reply...is Export / Import a reasonable possiblity here? I've not got lots of experience with it in a SQL Server environment (used it as an Oracle DBA many years ago), so don't know the practical use of it.