Word 2003: Error in VBA Help for built-in contants
Howard Kaikow
the list of WdPaperTray constants,
"wdPrinterSmallFormalBin" should be "wdPrinterSmallFormatBin".
2. If one examines the list of WdCompatibility constants for the
Compatibility property, one will find at least 4 constants were omitted from
the list of WdCompatibility constants.
3. It would be really useful if MSFT would fix the Help for those and,
likely, other lists of built-in constants.
4. And , while they are at it, why not fix the other errors Help that have
been previously reported?
For example:
In Office 97, 2000, XP, and 2003, the object browser INCORRECTLY states "As
fmShiftState" when describing the KeyDown and KeyUp events.
"As fmShitState" needs to be "As Integer" and list of allowed settings for
"Shift" needs to be corrected accordingly.
This problem was reported by a user in microsoft.public.word.vba.userforms
back in August 2002, plenty of time to fix a Help file.
--
http://www.standards.com/; See Howard Kaikow's web site.
Cindy M -WordMVP-
> It would be really useful if MSFT would fix the Help for those and,
> likely, other lists of built-in constants.
>
Yeah, I complained about some of these lists during beta. It was
really interesting: by the time we got to see any Help files it was
already too late to make any corrections/changes <snort>
But I'll be more than happy to pass these on. If things work as
they're supposed to, the changes will be made in the on-line version
of the Help. And hopefully also in any SP release that includes Help
files.
When in doubt, I make sure to use the Object Browser to get wd
Enum Constants!
BTW, was the mistype of "fmShiftState" (missing "f") at the end of
your message intentional, or a Freudian slip <g>?
Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Sep 30 2003)
http://www.mvps.org/word
This reply is posted in the Newsgroup; please post any follow
question or reply in the newsgroup and not by e-mail :-)
Howard Kaikow
news:VA.00008b21.006d1848@speedy...
> Yeah, I complained about some of these lists during beta. It was
> really interesting: by the time we got to see any Help files it was
> already too late to make any corrections/changes <snort>
That's a flawed SQA/development process.
If modifying Help files has side-effects on the code, then the code is in
real trouble.
> But I'll be more than happy to pass these on. If things work as
> they're supposed to, the changes will be made in the on-line version
> of the Help. And hopefully also in any SP release that includes Help
> files.
I have no faith that MSFT ever corrects such things.
> When in doubt, I make sure to use the Object Browser to get wd
> Enum Constants!
I would not trust the Object Browser, only the typelib.
I've saved a copy of the type library so I can search with, say, Wordpad.
Cindy M -WordMVP-
> I have no faith that MSFT ever corrects such things.
>
Oh, they do. And I have confirmation that these have been
entered in the bug database.
As to your other question, about wdUserOptionsPath:
This is a left-over from Word 2.0 (or so) and is only still
in the object model for reasons of backwards compatibility.
I understand one would like to remove it, but is concerned
about applications that have been brought forward over the
last decade that might rely on it.
There used to be an equivalent setting in Tools/Options in
the UI, but that has been removed.
Cindy