Re: Creating a visible field with a hidden component?
- From: "ML" <schooner@xxxxxxxxxxxxx>
- Date: Wed, 8 Feb 2006 19:42:15 -0400
Thanks.
Already have used conditional headers and footers. It was too simplistic
for our needs and thus why I am trying to extend the concept. We have too
many possibilities to code them all using the conditional method. As is
with conditional we ended up with about 10-12 combinations for 2 separate
fields but now we have even more, plus we also need to handle freeform text
values that a user may enter into our tags.
"Peter Jamieson" <pjj@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eke8$RQLGHA.3272@xxxxxxxxxxxxxxxxxxxxxxx
First, if you want a hidden component, there are various fields that do
not display a result that you could adapt. The simplest is probably SET,
e.g.
{ SET X info1 info2 info3 }
You could also try { ADDIN } or { PRIVATE }, assuming there is no reason
to believe they are being used for any other purpose.
Given the type of thing you're attempting you might find the last part of
http://gregmaxey.mvps.org/Conditional_Headers_Footers.htm
useful.
Peter Jamieson
"ML" <schooner@xxxxxxxxxxxxx> wrote in message
news:ujqdCiOLGHA.2780@xxxxxxxxxxxxxxxxxxxxxxx
The user will be inserting these on specific pages. When I parse for
the field I then need to determine what page it is on. So there is no
way to use a DocVariable at time of insertion because the page an item is
on may change as content is added to the document.
Basically I am creating a page level dynamic tag which is used to insert
classification markers and related information used to tag content of a
paragraph. So a given page and multiple pages may contain multiple
markers that re the same or different. When the page is parsed I then
generate a page specific docvarible, which is in turn used to set a page
specific header/footer element.
"Charles Kenyon" <wordfaq@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:u5nuTYOLGHA.984@xxxxxxxxxxxxxxxxxxxxxxx
Use a DocVariable for the SEQ label and a DocVariable field to
incorporate it in the SEQ field. For that matter, why not simply use
document variables to hold what you are parsing for unless you need it
in a particular place in the document body?
--
Charles Kenyon
Word New User FAQ & Web Directory: http://addbalance.com/word
Intermediate User's Guide to Microsoft Word (supplemented version of
Microsoft's Legal Users' Guide) http://addbalance.com/usersguide
See also the MVP FAQ: http://word.mvps.org/FAQs/ which is awesome!
--------- --------- --------- --------- --------- ---------
This message is posted to a newsgroup. Please post replies
and questions to the newsgroup so that others can learn
from my ignorance and your wisdom.
"ML" <schooner@xxxxxxxxxxxxx> wrote in message
news:u6843UOLGHA.3260@xxxxxxxxxxxxxxxxxxxxxxx
Well considering the SEQ part needs to be dynamic the autotext approach
is not an option.
"Charles Kenyon" <wordfaq@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:e67UATOLGHA.3728@xxxxxxxxxxxxxxxxxxxxxxx
The easiest way to insert nested fields is to create them manually
rather than through code and then save them as AutoText. To insert the
field using code, you then insert the AutoText entry.
--
Charles Kenyon
Word New User FAQ & Web Directory: http://addbalance.com/word
Intermediate User's Guide to Microsoft Word (supplemented version of
Microsoft's Legal Users' Guide) http://addbalance.com/usersguide
See also the MVP FAQ: http://word.mvps.org/FAQs/ which is awesome!
--------- --------- --------- --------- --------- ---------
This message is posted to a newsgroup. Please post replies
and questions to the newsgroup so that others can learn
from my ignorance and your wisdom.
"ML" <schooner@xxxxxxxxxxxxx> wrote in message
news:ueC2CmNLGHA.3396@xxxxxxxxxxxxxxxxxxxxxxx
I need to create a field that will be inserted via VBA code. This
will be made up of nested fields. The outer field will use a Quote
field with a visible text element that will show in the document.
Along with this is a nested field which contains tags that I will
parse for with another macro. The issue is I need to make the second
nested field not visible and also easily parsable in code. I'm
thinking of storing a delimited string in this field to contain the
various elements need later.
The only way I can think to do this is using the SEQ field with the
\h. Is this the only/best approach?
Here is what I want or similar:
{ QUOTE (CAUKEO) { SEQ AA-BB-CCCC \h } }
So later on I want to parse out the SEQ field associated with the
QUOTE and based on what it contains (i.e. does it include AA then..)
do something in the macro.
Any thoughts or insight on this approach?
.
- Follow-Ups:
- Re: Creating a visible field with a hidden component?
- From: Peter Jamieson
- Re: Creating a visible field with a hidden component?
- References:
- Creating a visible field with a hidden component?
- From: ML
- Re: Creating a visible field with a hidden component?
- From: Charles Kenyon
- Re: Creating a visible field with a hidden component?
- From: ML
- Re: Creating a visible field with a hidden component?
- From: Charles Kenyon
- Re: Creating a visible field with a hidden component?
- From: ML
- Re: Creating a visible field with a hidden component?
- From: Peter Jamieson
- Creating a visible field with a hidden component?
- Prev by Date: Re: Creating a visible field with a hidden component?
- Next by Date: Re: Creating a visible field with a hidden component?
- Previous by thread: Re: Creating a visible field with a hidden component?
- Next by thread: Re: Creating a visible field with a hidden component?
- Index(es):
Relevant Pages
|
