Great article, makes the creation on scripts much easier.

The only thing that is missing from the process is the permissions for each object they are not created, and as a result I have to create these manually. 

This only works for simple databases as it does not take account of dependencies between objects and can create objects in the wrong order.

Thanks for the comments guys, useful feedback like this is always much appreciated.

Unfortunately, yes, scripting of the table & stored proc security permissions does seem to be a limitation of this method, and was something I spotted only after submitting this article. It did make me wonder why it had not been included by MS - I'd have expected to see them applied after each object definition, or perhaps in a separate file.
Other than manually scripting them I'm afraid I can't offer a reasonable way around this at present.

With regard to the object order, probably the best way to deal with that is to do it with a number of passes, and not drop the objects which have already been created between each run of the script.
It's messy as you'll get lots of 'object already exists' errors, but at least it does eventually solve the creation order dependency problem.
How MS get around this in the upgrade scripts is something of a mystery, but it might explain why they take so long to run.

Intersting article, and actually, I just finished one similar tool with a set of different features.

I have been facing migrating database objects (several hundered sometimes)from tens of databases in different environments to some other environments.

I will probably send my article to Steve sometime next weekend to share with all others.

I guess you can use DTS to create a central repository for all these scripts.  Great article, Thanks!