Jay,
Thanks.

Signature
Greg Maxey/Word MVP
A Peer in Peer to Peer Support
> Hi Greg,
>
[quoted text clipped - 61 lines]
>>>> Greg Maxey/Word MVP
>>>> A Peer in Peer to Peer Support
But just to be picky, if .Text isn't the default property of a .Range, what
is. Or, perhaps the question should be "Under what circumstances might
.Text not be the default property of a range?" If there are none, why
shouldn't you rely on the default property?

Signature
Please post any further questions or followup to the newsgroups for the
benefit of others who may be interested. Unsolicited questions forwarded
directly to me will only be answered on a paid consulting basis.
Hope this helps
Doug Robbins - Word MVP
> Hi Greg,
>
[quoted text clipped - 62 lines]
>>>> Greg Maxey/Word MVP
>>>> A Peer in Peer to Peer Support
Jay Freedman - 29 Dec 2004 04:08 GMT
>But just to be picky, if .Text isn't the default property of a .Range, what
>is. Or, perhaps the question should be "Under what circumstances might
>.Text not be the default property of a range?" If there are none, why
>shouldn't you rely on the default property?
Hi Doug,
Maybe "rely on" isn't the right phrase... What I had in mind is "the
whole idea of 'default property' is an abomination and shouldn't be
used". :-) The reason to use explicit properties is mainly for human
understanding. I don't want to have to remember what the default
propery is for each of a few dozen object types.
Down the road, who knows what Microsoft may pull on us? Note that
there are no default properties in C# -- a design decision that I
endorse completely.
--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org
Word Heretic - 29 Dec 2004 18:48 GMT
G'day Jay Freedman <jay.freedman@verizon.net>,
Amen. It has taught me some nasty habits I find really hard to break.
The most common one I see / use erroneously is ActiveDocument.<assumed
content story range>
Steve Hudson - Word Heretic
steve from wordheretic.com (Email replies require payment)
Without prejudice
Jay Freedman reckoned:
>Down the road, who knows what Microsoft may pull on us? Note that
>there are no default properties in C# -- a design decision that I
>endorse completely.