Self-converting AutoTextList?

[JustSomeGuy]

Is it possible to tweak the AutoTextList syntax so that after the user
selects an item from the AutoTextList, a CTRL+SHIFT+F9 executes,
automatically converting the selected item to regular text?

 

[JustSomeGuy]

Purpose: distribute templates with autotextlist items embedded, that un-savvy
users can use, without having to know aobut and fuss with ctrl-shift f9 to
convert them all manually to plain text when they're done. The AutoTextList
items would each convert themselves, as part of their functioning, as soon
as the user makes a selection, as a last step in their execution.

 

[Russ]

Mr./Dr. JustSomeGuy,
If you are just sending out printed copies, then there is no need to change
the fields to plain text. How does it look in Print Preview mode?
Currently, AutoTextLists, in my Word version don't have a switch/option to
automatically revert to plain text. The benefit of not using that type of
option is that you can change your choice later.

If your intent was to send feedback to Microsoft, then you chances are
better if you look under the Word/Help menu for a Feedback menu choice. This
forum is read mainly by users and not Microsoft employees, necessarily.

If you need to send the actual file to a 'customer', then I see the need to
'fix the text' in the document.
Macros could be written to change the fields, or copy and paste as plain
text, but that would require another active effort by the user to activate
the macro, unless you intercept and use your own macros for all the possible
commands that Word has to Save a file or MailTo:, etc.

But I think Microsoft is content that AutoTextLists serve their purposes for
MailMerge templates, etc.

 

[JustSomeGuy]

Russ,
Thanks for the ideas - but in this case what is sought really is a
self-converting autotextlist; ie, some way of invoking the autotextlist
function packaged with or somehow paired with a macro or tricky vbasic code
snippet or whatever it takes to make the autotextlist function as a
self-terminating, one-time-only choice. The intent was indeed to pose the
idea to the user community which rarely disappoints each other with their
inventiveness and willingness to engage in envelope-stretching ideas and
solutions just for the sheer fun of helping to make things work. Kind
regards, JSG