Content Control Checkbox Hide and Show Text

Anything you do to show/hide content by toggling the font properties is unreliable in a corporate environment. That's because whether text formatted as hidden actually displays or prints has little to do with that property. Rather, it all depends on how the user has Word configured. Depending on that configuration, text formatted as hidden may:
• neither display nor print
• display but not print
• print but not display
• both display and print

Although it's probably safe to programmatically turn off the hidden-text printing, users may not appreciate you fiddling with its display, since toggling it off also toggles off the display of other formatting, such as spaces, tabs & paragraph breaks.

If you really want to control what happens, you need to conditionally insert/delete the content. To do that, try:

Please Login or Register  to view this content.

There are two issues with this approach:
1. Bookmarks are all too easily deleted by ham-fisted users, breaking the process; and
2. Doing anything more than simple text output requires considerably more coding.

An alternative approach, which would allow the content to remain in the document would be to use Custom Document Properties and field coding. This is easier for users to maintain and simplifies anything you might want to do that entails formatting:

Please Login or Register  to view this content.

With this approach, you don't need any bookmarks and the same Custom Document Property can be used to update multiple locations in the document - all you need is a field coded along the lines of the following for each:
{IF{DOCPROPERTY Chk1}= 1 "True Text"} or:
{IF{DOCPROPERTY Chk1}= 1 "True Text" "False Text"}
where field brace pairs (i.e. '{ }') are created in the document itself, via Ctrl-F9 (Cmd-F9 on a Mac); you can't simply type them or copy & paste them from this message. The output can contain pictures and tables as well as text. You create the Custom Document Properties via File|Properties|Advanced Properties>Custom. With this approach, the content remains in the document and is readily accessible by pressing Alt-F9 to reveal the field contents. It's still possible to show & print the field codes instead of their values but, since few users want to do either, the macro can fairly safely turn both of those options off.

Originally Posted by schmidt1962

Paul - first off Thank you! I appreciate you taking the time to respond.

I do have another couple of questions:

What is the difference between these two?
{IF{DOCPROPERTY Chk1}= 1 "True Text"} or:
{IF{DOCPROPERTY Chk1}= 1 "True Text" "False Text"}

The difference is that the second version has a 'false' result as well as the 'true' result. IF fields in Word don't need the explicit inclusion of a 'false' response.

Also, I presume "True Text" is the text that I want to toggle on (visible) or off (not visible). I highlight this in the document, push ctrl-F9 (to get brackets), which results in:

{"True Text"}

You shouldn't be seeing any braces or quote marks, just the text between them. You can't just type the fields or copy/paste the code from here into your document. All the field braces (i.e. { }) have to be created in the document itself via Ctrl-F9 or via Insert|Quick Parts|Field. Ctrl-F9 is far simpler, though. If you need to see & edit the field codes, pressing Alt-F9 will toggle their display on/off.

The part I don't understand is: IF{DOCPROPERTY Chk1}= 1. All I want visible to the users is the Text, and when I attempt to do the above see "IF{DOCPROPERTY Chk1}= 1" in the document. Also what if Chk1 = 0 (box is unchecked)? Thanks.

Once created properly, the fields should behave as described.

Without wanting to place too fine a point on it, none of your output text is enclosed within the required double quotes as indicated in the two examples I've given you. You also don't have the required space after the '=' sign. Furthermore, whereas I've specified a custom document property using 1 or 0, you've used one with 'Yes' or 'No'. A field that's looking for a 1 will treat both 'Yes' and 'No' as not 1.

Originally Posted by schmidt1962

now what is strange is I had to revise your code up above so it works

That suggests only that you had the true & false conditions in the field code switched around. Regardless, it's of no consequence.