You could add that functionality to your app. When they want to modify a template, create the original template doc for them and put it in whatever folder they want [strtofile(memo_fieldname, putfile())]. Then when they are done, have them replace the memo field with the new version of the template.

You can then assure that all users are working from the same template all the time. You can also design an archive to store all the previous versions of the template in case they screw up and need to revert back to a previous version.

If you leave the document out by itself, some user, someday will screw it up and there will be no backup version. Obviously my confidence in customers/users faithfully executing routine backup procedure is non-existent.

>I have about 80+ clients at about 25 sites in 5 states, me making any template changes for them is not an option. The are also very untechnical and they are accustom to being able to make changes to the main document after a merge. They would never be able to find their templates and they would lose their mind if they made a changes to a document created from a template and then the next time they mailmerged their change was not there. I do not want to have that phone conversation with them.
>
>Brenda
>
>>When they need template changes, I either do it, or I can at least more easily control such changes.