Attached Template Issue

I have a master template which contains quite a bit of VBA code. We send
this master template to department adminstrators who tweak and create sub
templates from the master. These sub templates are then distributed to the
staff who create their end documents. In the save event I programmatically
detach the "attached template" and re-attach the master template so at any
stage of the process the template and/or end docuement uses the VBA code from
the master. This has worked great (about two years) untill recently.
Although, the master is still attached to the end document (which I have
verfied by stepping through the code) it can not seem to find it. After some
research, I found MSDN article 823372 which describes mt issue perfectly.
This article provides a work around and a hotfix (hotfix not avaible to
general public until full regression testing has been completed but can get
it by calling microsoft) but neither one works as well as I hoped. After
days of testing I have come to beleive that an Office Security patch is the
culprit (KB887979).

My question is: Has anyone else had this issue? And does anyone know if
this Office Patch is in fact the culprit. I would perfer to leave it out of
any new ghost images we send to the field if it is infact the problem. I
know with several tests I would be able to answer my own question but I
thought I would ask to save some time.

Thanks

Jim F

Doug
Thu Jul 28 22:51:46 CDT 2005

I believe that your need to re-attach the master template so that the code
in it is available to the documents may be avoided by installing a template
that contains that code in each users Word Startup directory.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP
"Jim F" <JimF@discussions.microsoft.com> wrote in message
news:C08CEBED-5BB2-466C-B9A3-59E2D868B217@microsoft.com...
>I have a master template which contains quite a bit of VBA code. We send
> this master template to department adminstrators who tweak and create sub
> templates from the master. These sub templates are then distributed to
> the
> staff who create their end documents. In the save event I
> programmatically
> detach the "attached template" and re-attach the master template so at any
> stage of the process the template and/or end docuement uses the VBA code
> from
> the master. This has worked great (about two years) untill recently.
> Although, the master is still attached to the end document (which I have
> verfied by stepping through the code) it can not seem to find it. After
> some
> research, I found MSDN article 823372 which describes mt issue perfectly.
> This article provides a work around and a hotfix (hotfix not avaible to
> general public until full regression testing has been completed but can
> get
> it by calling microsoft) but neither one works as well as I hoped. After
> days of testing I have come to beleive that an Office Security patch is
> the
> culprit (KB887979).
>
> My question is: Has anyone else had this issue? And does anyone know if
> this Office Patch is in fact the culprit. I would perfer to leave it out
> of
> any new ghost images we send to the field if it is infact the problem. I
> know with several tests I would be able to answer my own question but I
> thought I would ask to save some time.
>
> Thanks
>
> Jim F
>

JimF
Fri Jul 29 06:35:03 CDT 2005

That's exactly what I did to resolve the issue temporarily. However, it's
not a good permanent solution because our auditors (in order to help bring us
in compliance with sarbanes oxly....thanks Enron!!!) have mandated that the
lowest macro security level we can have is medium....which prompts the user
to enable macros each time word is opened. I could sign the code with my
verisign digital signature but it exprires soon and we have no intention on
renewing it. I have templates and add-is trusted which did not over ride the
medium macro security.

Thanks.

"Doug Robbins" wrote:

> I believe that your need to re-attach the master template so that the code
> in it is available to the documents may be avoided by installing a template
> that contains that code in each users Word Startup directory.
>
> --
> Hope this helps.
>
> Please reply to the newsgroup unless you wish to avail yourself of my
> services on a paid consulting basis.
>
> Doug Robbins - Word MVP
> "Jim F" <JimF@discussions.microsoft.com> wrote in message
> news:C08CEBED-5BB2-466C-B9A3-59E2D868B217@microsoft.com...
> >I have a master template which contains quite a bit of VBA code. We send
> > this master template to department adminstrators who tweak and create sub
> > templates from the master. These sub templates are then distributed to
> > the
> > staff who create their end documents. In the save event I
> > programmatically
> > detach the "attached template" and re-attach the master template so at any
> > stage of the process the template and/or end docuement uses the VBA code
> > from
> > the master. This has worked great (about two years) untill recently.
> > Although, the master is still attached to the end document (which I have
> > verfied by stepping through the code) it can not seem to find it. After
> > some
> > research, I found MSDN article 823372 which describes mt issue perfectly.
> > This article provides a work around and a hotfix (hotfix not avaible to
> > general public until full regression testing has been completed but can
> > get
> > it by calling microsoft) but neither one works as well as I hoped. After
> > days of testing I have come to beleive that an Office Security patch is
> > the
> > culprit (KB887979).
> >
> > My question is: Has anyone else had this issue? And does anyone know if
> > this Office Patch is in fact the culprit. I would perfer to leave it out
> > of
> > any new ghost images we send to the field if it is infact the problem. I
> > know with several tests I would be able to answer my own question but I
> > thought I would ask to save some time.
> >
> > Thanks
> >
> > Jim F
> >
>
>
>

JimF
Fri Jul 29 12:40:56 CDT 2005

Just FYI.....Good news....bad news.

Through testing we have determined that Office Patch KB887979 does infact
cause the problem. Microsofts attempt to close some security holes and fix
office SP1 casued more problems. The bad news is that the hotfix MS provides
does not work worth a damn and the only way to unistall the office Patch is
to Unistall office completly...to include removing any office folder that are
left behind after the install...and then reinstall Office.


"Jim F" wrote:

> That's exactly what I did to resolve the issue temporarily. However, it's
> not a good permanent solution because our auditors (in order to help bring us
> in compliance with sarbanes oxly....thanks Enron!!!) have mandated that the
> lowest macro security level we can have is medium....which prompts the user
> to enable macros each time word is opened. I could sign the code with my
> verisign digital signature but it exprires soon and we have no intention on
> renewing it. I have templates and add-is trusted which did not over ride the
> medium macro security.
>
> Thanks.
>
> "Doug Robbins" wrote:
>
> > I believe that your need to re-attach the master template so that the code
> > in it is available to the documents may be avoided by installing a template
> > that contains that code in each users Word Startup directory.
> >
> > --
> > Hope this helps.
> >
> > Please reply to the newsgroup unless you wish to avail yourself of my
> > services on a paid consulting basis.
> >
> > Doug Robbins - Word MVP
> > "Jim F" <JimF@discussions.microsoft.com> wrote in message
> > news:C08CEBED-5BB2-466C-B9A3-59E2D868B217@microsoft.com...
> > >I have a master template which contains quite a bit of VBA code. We send
> > > this master template to department adminstrators who tweak and create sub
> > > templates from the master. These sub templates are then distributed to
> > > the
> > > staff who create their end documents. In the save event I
> > > programmatically
> > > detach the "attached template" and re-attach the master template so at any
> > > stage of the process the template and/or end docuement uses the VBA code
> > > from
> > > the master. This has worked great (about two years) untill recently.
> > > Although, the master is still attached to the end document (which I have
> > > verfied by stepping through the code) it can not seem to find it. After
> > > some
> > > research, I found MSDN article 823372 which describes mt issue perfectly.
> > > This article provides a work around and a hotfix (hotfix not avaible to
> > > general public until full regression testing has been completed but can
> > > get
> > > it by calling microsoft) but neither one works as well as I hoped. After
> > > days of testing I have come to beleive that an Office Security patch is
> > > the
> > > culprit (KB887979).
> > >
> > > My question is: Has anyone else had this issue? And does anyone know if
> > > this Office Patch is in fact the culprit. I would perfer to leave it out
> > > of
> > > any new ghost images we send to the field if it is infact the problem. I
> > > know with several tests I would be able to answer my own question but I
> > > thought I would ask to save some time.
> > >
> > > Thanks
> > >
> > > Jim F
> > >
> >
> >
> >