H
Howard Kaikow
1. If one goes to the Help for the DefaultTrayID Property and then clicks on
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.
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.