> I don't get quite the same as you say, but certainly not correct results.
>
[quoted text clipped - 107 lines]
> http://www.microsoft.com/office/community/en-us/default.mspx?mid=6752c14e-4d
> bc-43bd-a137-85809136c67c&dg=microsoft.public.word.vba.general
Hi Nick,
I certainly haven't exhaustively tested but the window size and position
didn't seem to make a difference for me. But, even accepting it as a bug,
this is all rather esoteric - under what real circumstances do you hit this
problem?
--
Enjoy,
Tony
> Hi Tony,
>
[quoted text clipped - 126 lines]
> > > link to open the suggestion in the Microsoft Web-based Newsreader and then
> > > click "I Agree" in the message pane.
http://www.microsoft.com/office/community/en-us/default.mspx?mid=6752c14e-4d
> > bc-43bd-a137-85809136c67c&dg=microsoft.public.word.vba.general
Jean-Guy Marcil - 26 Oct 2006 19:57 GMT
Tony Jollans was telling us:
Tony Jollans nous racontait que :
> Hi Nick,
>
> I certainly haven't exhaustively tested but the window size and
> position didn't seem to make a difference for me. But, even accepting
> it as a bug, this is all rather esoteric - under what real
> circumstances do you hit this problem?
And, to top it off... all this is predicated on using the Selection object,
which really should not be used as it is used in the example provided.
A Range objectis more reliable, faster and would certainly not create this
so-called bug.
This is just another example that re-enforces my conviction about not using
the Selection object unless I really need to...

Signature
Salut!
_______________________________________
Jean-Guy Marcil - Word MVP
jmarcilREMOVE@CAPSsympatico.caTHISTOO
Word MVP site: http://www.word.mvps.org