Shauna
Mon Sep 17 07:45:41 CDT 2007
Hi Paul
I suspect that Word often ascribes fault to the wrong party. It seems
unlikely that your one-liner would cause too much offence. Is it possible
that your users are using something else that is causing the problem? Do
they typically have other Word add-ins? Could those be causing the real
problem?
Hope this helps.
Shauna Kelly. Microsoft MVP.
http://www.shaunakelly.com/word
"Paul Hooper" <PaulHooper@discussions.microsoft.com> wrote in message
news:CFE56193-C0CC-4F4E-A81F-2C4888516F5D@microsoft.com...
> Hi Russ,
>
> Currently, our templates are stored in the "wrong" startup directory in
> the
> Word program subdirectory. We store them there because our customers are
> schools, and their networks are typically run by relatively inexperienced
> sysadmins and the thought of writing the sort of startup script you are
> describing would be an horrendous to most of them. Your reply implies
> that
> if this is file is "non-local" (probably on a network share) then this
> might
> prompt the problem. You may well be right but we have seen the problem on
> stand-alone machines as well - the template is still in the "wrong"
> directory
> but is certainly local.
>
> You may be on to something however as our Office 2007 templates, which are
> stored in the user profiles, do not seem to experience the same effect,
> although we have very few customers using Office 2007 at this time.
>
> I am still confused by the intermittent nature of the problem. Many
> customers go years before Word spits the dummy and turns off the template.
>
> Thanks for your thoughts in any case. Maybe we need to look to store the
> templates in the User Profiles, where they should be, but that just
> creates
> another set of headaches as we try to help sysadmins propagate the
> templates
> across their users.
>
> Paul
>
> "Russ" wrote:
>
>> Paul,
>> There have been discussions in this forum recommending that one of the
>> best
>> ways to handle templates in a group or network is to have each Computer
>> start-up script check for new templates and download them to the local
>> hard
>> drive, if they are new. Then, when someone starts Word, they use the
>> local
>> copies of the templates.
>> Local being the key word.
>> Also regular users don't normally alter a template, but create a new
>> document based on a template (normal.dot is the default template).
>> Do any of this help in your case?
>>
>> > We have a number of very simple DOT files that contain a one-line macro
>> > and a
>> > toolbar that are used to automate access to a product. The one-line
>> > macro is
>> > an ActiveDocument.Shapes.AddOLEObject command that is only invoked when
>> > the
>> > toolbar button is pushed.
>> >
>> > The full line is
>> >
>> > ActiveDocument.Shapes.AddOLEObject Anchor:=Selection.Range, ClassType:=
>> > "FXDraw3.Document", FileName:="", LinkToFile:=False,
>> > DisplayAsIcon:=False
>> >
>> > Our problem is that Word (particularly, but not exclusively Word 2003)
>> > seems
>> > to disable this template file on irregular occasions. Users need to go
>> > to the
>> > Templates and Add-Ins screen to re-enable them which is annoying for
>> > everyone. Sometimes Word complains that the "last time this template
>> > file
>> > was run, it caused a serious problem" when the template file is
>> > enabled.
>> >
>> > Interestingly, another template file that still uses a
>> > WordBasic.InsertObject command does not seem to be susceptible to the
>> > problem
>> > - but that may be because that particular product is much less popular.
>> >
>> > So the question is... Does anyone know of anything that could be
>> > triggering
>> > this behaviour in Word?
>> >
>> > Thanks in anticipation.
>> >
>> > Paul Hooper
>>
>> --
>> Russ
>>
>> drsmN0SPAMikleAThotmailD0Tcom.INVALID
>>
>>