![]() Some interesting things I noted while experimenting further. There but I still received the warning message that it would be read only. When attaching the template from that location I did receive the message you mentioned so I added the location as a shared template area, checked the registry and the value was Next I moved it to the P drive, which is a network server drive in our office. Read and execute yes but not any write permission. A non-administrator user would not have full control of it. However that the security permissions changed on the template when I placed it on the D drive. ![]() I then I moved it to the local D drive on my system and it attached fine with no messages and I could execute various macros. I put a dotm template that has lots of macros into another location on my C drive and as you said there was no problem. ![]() Well from my testing it does appear to be an issue of location. My client however, wants to use my addin on both Word 2007 as Word 2010 systems.Īre there plans to include this fix in a ‘normal’ update for both Word 2007 as Word 2010 or do I need to tell my client to install this fix on all systems? I found a reference to a hotfix describing this behavior ( ). It’s not caused by the addin, because I see the same behavior if I load Word without addins and try to do it manually. ![]() This behavior can be reproduced if you change the attached template manually. Templates on a network drive – or even the local D: drive for that matter – all give the error. I found that this error only kicks in whenever the. dotm template, I receive an error that the template is locked for editing. The code works fine as long as I attach a. I have created a Word addin which sole purpose is to change the attachedtemplate of specific documents. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |