I hadn't thought of using the directory link, we use something similar for our SQL Prompt snippets rather than templates.
What if one of your users wanted to have their own version of something, and didn't want to share? This is our (my) situation, and our solution was to create a cmd file that sits in the startup folder, and copies down the scripts from the shared location to the local directory on login.
In this way, I still get shared scripts, I can still save the ones I want to share to the main location, but I can develop my own without worrying about cluttering up everyone else's.
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."