> Our application integrates tightly with Word using automation.
>
[quoted text clipped - 11 lines]
> attach to an existing instance of Word AND it was already maximised
> then this is where we have the issue).
There are a couple of instances where we do want to activate Word, ie
to show the results of a spellcheck and to show the document that has
been automatically produced (to give the user the option to change).
I neglected to say in the original post that we are also calling the
Activate() method.
> The better (and easier) solution is to make sure that Word doesn't display
> any dialogs. If your application is (as you claim) tightly integrated, this
[quoted text clipped - 15 lines]
> > attach to an existing instance of Word AND it was already maximised
> > then this is where we have the issue).
Jezebel - 19 Oct 2006 13:18 GMT
If Word is activated, then dealing with the dialogs is the user's
responsibility. You really can't have it both ways: either Word is under
your app's control, or it's under your user's control.
> There are a couple of instances where we do want to activate Word, ie
> to show the results of a spellcheck and to show the document that has
[quoted text clipped - 24 lines]
>> > attach to an existing instance of Word AND it was already maximised
>> > then this is where we have the issue).
PromisedOyster - 20 Oct 2006 12:41 GMT
Yes I understand this. All I am asking for is for is the Word
Automation commands to ensure that Word gets focus as the Activate()
nor the SetFocus() command does not always seem to work.
> If Word is activated, then dealing with the dialogs is the user's
> responsibility. You really can't have it both ways: either Word is under
[quoted text clipped - 28 lines]
> >> > attach to an existing instance of Word AND it was already maximised
> >> > then this is where we have the issue).