M
MikeS_NZ
Our organization has Word 2007 configured with the startup folder on a
network share. In the startup folder is a dotm file containing a library of
commonly used code. Our company templates all reference the code in the
startup library.
With either Office 2007 service pack 2 or KB956358 installed Word changes
its handling of our startup library and our code breaks. Word appears to no
longer trust the code in the startup library.
If we move the startup folder to a non-network location, then Word behaves
correctly. Note - we have the network startup folder added as a “trusted
locationâ€, and have the “Allow trusted locations on my network†option
enabled.
The fault can easily be reproduced using the following steps: Create a new
dotm file, enter the VBA IDE and create a new module. Save the new template
onto a network folder, then reconfigure Word to use the network folder as its
startup folder.
Restart word, and enter the VBA IDE. Word should have loaded the new project
in the project explorer window. If you then attempt to add it as a reference
to the current document, it will throw an error “Requested type library or
object is not a vba projectâ€. If you change nothing but move the startup
folder to a not-network location, Word will behave correctly.
Is this an intentional change in behaviour or a bug that has been introduced?
If it’s a bug, then is there a patch available? If the change in behaviour
is intentional, then is there anything we can do to reverse the behaviour?
network share. In the startup folder is a dotm file containing a library of
commonly used code. Our company templates all reference the code in the
startup library.
With either Office 2007 service pack 2 or KB956358 installed Word changes
its handling of our startup library and our code breaks. Word appears to no
longer trust the code in the startup library.
If we move the startup folder to a non-network location, then Word behaves
correctly. Note - we have the network startup folder added as a “trusted
locationâ€, and have the “Allow trusted locations on my network†option
enabled.
The fault can easily be reproduced using the following steps: Create a new
dotm file, enter the VBA IDE and create a new module. Save the new template
onto a network folder, then reconfigure Word to use the network folder as its
startup folder.
Restart word, and enter the VBA IDE. Word should have loaded the new project
in the project explorer window. If you then attempt to add it as a reference
to the current document, it will throw an error “Requested type library or
object is not a vba projectâ€. If you change nothing but move the startup
folder to a not-network location, Word will behave correctly.
Is this an intentional change in behaviour or a bug that has been introduced?
If it’s a bug, then is there a patch available? If the change in behaviour
is intentional, then is there anything we can do to reverse the behaviour?