microsoft.public.word.vba.general

I found a workaround for this. If you make the templates that reside in the
startup folder read-only, ther error is not displayed when you start a second
Word session.

"klav" wrote:

> We have an application that uses javascript code to open a new instance of
> Word, even if there is already an instance running. This worked fine with
> Word 2003, even if there was already a Word sesion open. I could have
> multiple Word sessions open and the javascript code would not complain.
>
> I am in the process of converting things for Word 2007 and this code still
> works with 2007 except that if Word is already opened when I run the
> javascript code, I get an error because there are some templates in the
> startup folder that are already loaded. The error tells me that
> "templatename".dotm is locked for editing. I don't want to kill the prior
> Word session; I simply want to keep the session that javascript opens
> separate.
>
> The javascript code uses the following code:
>
> new ActiveXObject("Word.Application")
>
> This establishes the new instance of Word. I know there is a startup switch
> /a that will not load any templates, including normal.dot but I'm not sure
> how to do that with javascript with this existing code and I don't know if
> that's the correct approach anyway.
>
> Does anyone have any ideas on how I can get this to work? Is there some
> setup option in Word that specifies how to handle multiple Word sessions? Any
> help is greatly appreciated. Thanks.