Office Word 2003

[Gilligan]

I have a question about the Word 2003 architecture. I was under the
impression that Word 2003 was base on MDI architecture and only a single word
process would exist. The issue is that an application I am using is
embedding word into there program. At times there will be two or three
processes of word running in the task manager. Should there ever be more
then one word process in office 2003?

[Tony Jollans]

This is poorly understood and often misrepresented.

Word is an SDI application - the default, and underlying architecture, is to
present a *S*ingle *D*ocument in the *I*nterface. It mimics an MDI if asked.
(By contrast, Excel is an MDI application that mimics SDI).

Independently, and regardless, Word is a multiple use application and you
can have many instances running concurrently and they will not interfere
with each other, except insofar as they use the same files - there is only
one normal template, for example. Again by contrast, Outlook is a single use
application and any attempts to create a second instance will connect to an
existing running one instead of creating a new one.

--
Enjoy,
Tony

"Gilligan" <Gill...@nospam.nospam> wrote in message
news:4C65C39E-A5FA-43B7...@microsoft.com...

[Gilligan]

Thank you for your explanation.

Could you give me a link to help understand then how the application menus
are controlled. I started an instance of the Word 2003 application and
change the menu bar and the title. Then I started word and the same change
were made the the application. How do I control the applications that are
being selected selected for the desktop vs the Word applications that is
started in a C# application.

Thank you again for your help.

[Tony Jollans]

Firstly let me correct myself - my description was correct but my
terminology was wrong - Word is called a single use application (and Outlook
a multiple use one).

When you make a change to a menu, say, it is stored in whatever container
you tell Word - by default, usually, normal.dot - in memory. That change
doesn't exist anywhere else until the container is written to disk,
explicitly by you or possibly implicitly at application end. It will not be
picked up by another instance of the application unless it has been saved.
So ...

I'm not absolutely certain from your description what action you are taking,
but it sounds like the second invocation is not creating a second instance.
if I understand you, you are starting Word via automation - and then making
it visible? - and making some changes - and then "starting" Word manually
through Windows. If that is so, Windows will attach to the running instance.
If you are doing something else, please describe it in more detail.

--
Enjoy,
Tony

"Gilligan" <Gill...@nospam.nospam> wrote in message

news:5EE66AC2-E2AB-4E1F...@microsoft.com...