microsoft.public.word.vba.general

"kalukaley" wrote:

> We're using automation to create MS Word documents. Borland C++ builder (I
> am in the process of converting the code for use in Visual Studio) is what
> we're using.
>
> We just started encountering the following intermittent problem.
>
> When the application object calls set_visible the application appears to
> hang. Turns out that it's not. If you wait about 15 minutes (that's not an
> exaggeration) word will finally open a document and go on to run the rest of
> the code to completion.
>
> The com object targets word 2000. the version of word we're running is
> 2002, and the environment is Citrix (Windows server 2003).

Citrix always slows things down as the application is shared, not actually
on the local machine.
If you are targeting Word 2000, why are you running Word 2002?
If setting to visible slows things down to a screeching halt, and since you
are automating a process, why don't you just let the application run
invisible?