D
Danny O'Hern (ohernova
Include commonly reported exceptions for each Office function as a link in
online help, at the function help dialogue screen. Microsoft is collecting
questions and problem descriptions from the field, so they should be included
as a link to the database from the function help screen, and all exceptions
that relate to that function can be available to everyone, which would reduce
server time for fruitless searches. Too often, the step-by-step description
of how a function would be used do not include exceptions that occur often
and are not explained. For example, in Microsoft Office Word the Tool
command for Letters and Mailings contains several options that should be in
bold, but sometimes are faded and there is no explanation for what causes
those commands, such as "Envelopes and Labels", to be unavailable. Why does
this happen, and what is the workaround? That should be answered through a
link to "Common exceptions to this Command Instruction", which would be
linked to the database built on user comments and questions for each command
and function. If the exception is not listed, as in "Command faded and not
available", then there could be a choice to pose the question, which would
link to the database for that command. If enough users pose the same
question, that "fix" would be then included in the common exceptions
eventually, and users would not have to pose that question. We want answers
so we can continue working. We don't mean to use up your server time,
increase corporate costs, and waste time on a deadline on fruitless searches.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
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/com...-c4817419feb2&dg=microsoft.public.office.misc
online help, at the function help dialogue screen. Microsoft is collecting
questions and problem descriptions from the field, so they should be included
as a link to the database from the function help screen, and all exceptions
that relate to that function can be available to everyone, which would reduce
server time for fruitless searches. Too often, the step-by-step description
of how a function would be used do not include exceptions that occur often
and are not explained. For example, in Microsoft Office Word the Tool
command for Letters and Mailings contains several options that should be in
bold, but sometimes are faded and there is no explanation for what causes
those commands, such as "Envelopes and Labels", to be unavailable. Why does
this happen, and what is the workaround? That should be answered through a
link to "Common exceptions to this Command Instruction", which would be
linked to the database built on user comments and questions for each command
and function. If the exception is not listed, as in "Command faded and not
available", then there could be a choice to pose the question, which would
link to the database for that command. If enough users pose the same
question, that "fix" would be then included in the common exceptions
eventually, and users would not have to pose that question. We want answers
so we can continue working. We don't mean to use up your server time,
increase corporate costs, and waste time on a deadline on fruitless searches.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
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/com...-c4817419feb2&dg=microsoft.public.office.misc