script language in header/footer

See Word's Help on the topic "Field codes: StyleRef field."

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.

"inadmissible3" wrote in message
...
Suzanne,

How do I do this StyleRef field?

Thank you.

"Suzanne S. Barnhill" wrote:

Alternatively, if the desired text appears in the document itself and
the
field is formatted with a unique character style (which can be identical
to
the Default Paragraph Font), a StyleRef field in the header will pick up
the
text as it is replaced.

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the
newsgroup so
all may benefit.

"Jay Freedman" wrote in message
...
Ah, the light is starting to dawn...

What I suspect is happening is that Amicus Assembly does a
find-and-replace operation during the generation, looking for things
surrounded by the %[ and ] markers and replacing them with data
according to the quoted name.

The problem is that headers and footers are in a separate area of the
file (Word's technical term is "story") from the main text, and a
find-and-replace operation has to do some special work to find things
in those other stories. (This is explained at
http://www.word.mvps.org/FAQs/Custom...ceAnywhere.htm.) It
seems that Amicus Assembly doesn't do that extra work.

You might try bookmarking the scripts in the body text and using
cross-references to those bookmarks in the header. There's a gotcha
there, as well, though: when Amicus Assembly replaces the scripts, it
will probably overwrite and destroy the bookmarks (extra work is
required to keep them), and then the cross-references will show error
messages to the effect that the bookmarks don't exist.

I don't think there's really anything you can do except complain to
the company (Gavel & Gown Software) that their product lacks
functionality that you need. Send them the URL cited above, and
request an update.

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org

On Tue, 3 May 2005 12:11:07 -0700, "inadmissible3"
wrote:

Here is a sample of the script language that is from Amicus
Assembly-document
assembly program-

%[Matter.CustomField("Case Name")]
%[Matter.CustomField("County")] %[Matter.CustomField("Case No.")]

When this information is filled out when setting up the case file,
and I
want to generate a document, this script language translates to text
and
shows to the proper case name and case number in the document. When
I do
this in the body of the document, it works fine, but when i copy this
script
language inside the header/footer, it will not/does not show anything
but
the
script language shown above.

Is there anything I can do? Thank you.
"Jay Freedman" wrote:

I'm sorry, but it still isn't making much sense to me, probably
because we're using the same words with different meanings.

Word has several classes of "fields", with many specific kinds
within
each class. These are the ones that seem to have the most probable
connection to what you're doing:

- Plain "fields" are the class of fields created by the Insert
Field
dialog, or by pressing Ctrl+F9, or by a macro that contains an
ActiveDocument.Fields.Add statement. If you look in the Insert
Fields dialog, you'll see a couple of dozen kinds. Some that might
be
used by your document creation program to display information (like
case name and number) are the Quote field, the DocProperty field,
the
DocVariable field, and the Reference field. Each kind of field has
a
specific purpose, as described in Word's help file, but they can
often
be "bent" to other purposes. Most fields of this class operate
perfectly well in headers/footers as easily as in regular body
text.

- "Form fields" are for use in a "protected form". The idea here is
that you set up a document containing both static text and
changeable
fields; once the document is protected, the static text can't be
selected or edited and only the fields are available. Word
prohibits
form fields in headers and footers -- so I suspect this is what
you're
trying to use.

- Controls in userforms (custom dialogs) are sometimes called
"fields"
although this is something of a misnomer. This isn't related at all
to
your problem.

Then there are combinations of fields... If the document generating
program is inserting form fields in the body of the (protected
form)
document, you can place a Reference field in the primary
(non-first-page) header to repeat that information. The form field
has
a "bookmark name", which you can see in its Properties dialog; the
Reference field needs to refer to that name. See part 2 of
http://gregmaxey.mvps.org/Repeating_Data.htm for illustrated
instructions.

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org

On Tue, 3 May 2005 10:05:07 -0700, "inadmissible3"
wrote:

Yes, I am using a document generating program whereby I have
fields
inserted
into a blank document that are populated by the information found
in a
client
file. What i am attempting to do is to have the case name and
number
as a
header on the second page and every page thereafter. The "script
fields"
polulate outside the header, but do not work within a
header/footer.
Make
sense?

Thank you again.

"Jay Freedman" wrote:

I suspect we're at cross purposes here about the meaning of
"script
language". I understood it to mean executable code that does
something, like
the VBscript or JavaScript that you can embed in an HTML page.
Your
later
description indicates that it's text that should appear on a
(viewed
or
printed) Word document. In that case it has nothing to do with
macros or
programming.

If your question is how to get the text to appear on the second
and
subsequent pages but not on the first page, the answer is to go
to
File
Page Setup, click the Layout tab, and check the box for
"Different
first
page". In the document, temporarily create a second page by
pressing
Ctrl+Enter at the end of page 1 to insert a page break. Open the
header
area. If there is text in the First Page Header, remove it.
Place
the text
in the header on page 2. Close the header area, and delete the
page
break.
Word will "remember" the header and display it on pages 2 and
beyond, when
the document becomes more than one page long.

This procedure is similar to the one described at
http://sbarnhill.mvps.org/wordfaqs/Letterhead.htm. The only
difference is
which header (First Page or the primary Header) you put the text
into.

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org

inadmissible3 wrote:
The script language from a document assembly program is like a
form
field that contains case name, number, etc. so when I want to
generate a document to a particular client, and the document
is
more
than one page in length, this information is in the
header/footer.

I have also posted the original question on the programming
group
as
well, but if you have any suggestions, I will listen.

Thank you.

"Jay Freedman" wrote:

On Mon, 2 May 2005 17:53:01 -0700, "inadmissible3"
wrote:

I have inserted some script language from another software
program
(Amicus Assembly) into and as a second (and subsequent) page
header, but it doesn't work...

Thank you for your patience.......

inadmissible3

There's no reason to believe that script language from any
other
program will work in Word. A Word document's header is
nothing at
all
like an HTML header except for the name.

You may need to reprogram the script as a VBA macro. What is
it
supposed to do? In any case, it would be best to move the
discussion
to the programming newsgroup,



http://www.microsoft.com/office/comm... lang=en&cr=US.

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org

Suzanne, I don't understand how to create a new StyleRef field or how to
insert it, name it. Please help.

Thank you.

"Suzanne S. Barnhill" wrote:

See Word's Help on the topic "Field codes: StyleRef field."

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.

"inadmissible3" wrote in message
...
Suzanne,

How do I do this StyleRef field?

Thank you.

"Suzanne S. Barnhill" wrote:

Alternatively, if the desired text appears in the document itself and
the
field is formatted with a unique character style (which can be identical
to
the Default Paragraph Font), a StyleRef field in the header will pick up
the
text as it is replaced.

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the
newsgroup so
all may benefit.

"Jay Freedman" wrote in message
...
Ah, the light is starting to dawn...

What I suspect is happening is that Amicus Assembly does a
find-and-replace operation during the generation, looking for things
surrounded by the %[ and ] markers and replacing them with data
according to the quoted name.

The problem is that headers and footers are in a separate area of the
file (Word's technical term is "story") from the main text, and a
find-and-replace operation has to do some special work to find things
in those other stories. (This is explained at
http://www.word.mvps.org/FAQs/Custom...ceAnywhere.htm.) It
seems that Amicus Assembly doesn't do that extra work.

You might try bookmarking the scripts in the body text and using
cross-references to those bookmarks in the header. There's a gotcha
there, as well, though: when Amicus Assembly replaces the scripts, it
will probably overwrite and destroy the bookmarks (extra work is
required to keep them), and then the cross-references will show error
messages to the effect that the bookmarks don't exist.

I don't think there's really anything you can do except complain to
the company (Gavel & Gown Software) that their product lacks
functionality that you need. Send them the URL cited above, and
request an update.

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org

On Tue, 3 May 2005 12:11:07 -0700, "inadmissible3"
wrote:

Here is a sample of the script language that is from Amicus
Assembly-document
assembly program-

%[Matter.CustomField("Case Name")]
%[Matter.CustomField("County")] %[Matter.CustomField("Case No.")]

When this information is filled out when setting up the case file,
and I
want to generate a document, this script language translates to text
and
shows to the proper case name and case number in the document. When
I do
this in the body of the document, it works fine, but when i copy this
script
language inside the header/footer, it will not/does not show anything
but
the
script language shown above.

Is there anything I can do? Thank you.
"Jay Freedman" wrote:

I'm sorry, but it still isn't making much sense to me, probably
because we're using the same words with different meanings.

Word has several classes of "fields", with many specific kinds
within
each class. These are the ones that seem to have the most probable
connection to what you're doing:

- Plain "fields" are the class of fields created by the Insert
Field
dialog, or by pressing Ctrl+F9, or by a macro that contains an
ActiveDocument.Fields.Add statement. If you look in the Insert
Fields dialog, you'll see a couple of dozen kinds. Some that might
be
used by your document creation program to display information (like
case name and number) are the Quote field, the DocProperty field,
the
DocVariable field, and the Reference field. Each kind of field has
a
specific purpose, as described in Word's help file, but they can
often
be "bent" to other purposes. Most fields of this class operate
perfectly well in headers/footers as easily as in regular body
text.

- "Form fields" are for use in a "protected form". The idea here is
that you set up a document containing both static text and
changeable
fields; once the document is protected, the static text can't be
selected or edited and only the fields are available. Word
prohibits
form fields in headers and footers -- so I suspect this is what
you're
trying to use.

- Controls in userforms (custom dialogs) are sometimes called
"fields"
although this is something of a misnomer. This isn't related at all
to
your problem.

Then there are combinations of fields... If the document generating
program is inserting form fields in the body of the (protected
form)
document, you can place a Reference field in the primary
(non-first-page) header to repeat that information. The form field
has
a "bookmark name", which you can see in its Properties dialog; the
Reference field needs to refer to that name. See part 2 of
http://gregmaxey.mvps.org/Repeating_Data.htm for illustrated
instructions.

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org

On Tue, 3 May 2005 10:05:07 -0700, "inadmissible3"
wrote:

Yes, I am using a document generating program whereby I have
fields
inserted
into a blank document that are populated by the information found
in a
client
file. What i am attempting to do is to have the case name and
number
as a
header on the second page and every page thereafter. The "script
fields"
polulate outside the header, but do not work within a
header/footer.
Make
sense?

Thank you again.

"Jay Freedman" wrote:

I suspect we're at cross purposes here about the meaning of
"script
language". I understood it to mean executable code that does
something, like
the VBscript or JavaScript that you can embed in an HTML page.
Your
later
description indicates that it's text that should appear on a
(viewed
or
printed) Word document. In that case it has nothing to do with
macros or
programming.

If your question is how to get the text to appear on the second
and
subsequent pages but not on the first page, the answer is to go
to
File
Page Setup, click the Layout tab, and check the box for
"Different
first
page". In the document, temporarily create a second page by
pressing
Ctrl+Enter at the end of page 1 to insert a page break. Open the
header
area. If there is text in the First Page Header, remove it.
Place
the text
in the header on page 2. Close the header area, and delete the
page
break.
Word will "remember" the header and display it on pages 2 and
beyond, when
the document becomes more than one page long.

This procedure is similar to the one described at
http://sbarnhill.mvps.org/wordfaqs/Letterhead.htm. The only
difference is
which header (First Page or the primary Header) you put the text
into.

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org

inadmissible3 wrote:
The script language from a document assembly program is like a
form
field that contains case name, number, etc. so when I want to
generate a document to a particular client, and the document
is
more
than one page in length, this information is in the
header/footer.

I have also posted the original question on the programming
group
as
well, but if you have any suggestions, I will listen.

Thank you.

"Jay Freedman" wrote:

On Mon, 2 May 2005 17:53:01 -0700, "inadmissible3"
wrote:

I have inserted some script language from another software
program
(Amicus Assembly) into and as a second (and subsequent) page
header, but it doesn't work...

Thank you for your patience.......

inadmissible3

There's no reason to believe that script language from any
other
program will work in Word. A Word document's header is
nothing at
all
like an HTML header except for the name.

You may need to reprogram the script as a VBA macro. What is
it
supposed to do? In any case, it would be best to move the
discussion
to the programming newsgroup,



http://www.microsoft.com/office/comm... lang=en&cr=US.

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org

You can use Insert | Field | StyleRef to insert the field. That part is
easy. Before you do that, however, you must create and apply your character
style. Just select Default Paragraph Font in the Styles dialog, click
New..., make sure that "Character" is selected as the style type, and type a
name for the new style. Then apply that style to the text in the document
that you want repeated in the header. Then insert the StyleRef field in the
header, referring to the style you just applied.

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.

"inadmissible3" wrote in message
...
Suzanne, I don't understand how to create a new StyleRef field or how to
insert it, name it. Please help.

Thank you.

"Suzanne S. Barnhill" wrote:

See Word's Help on the topic "Field codes: StyleRef field."

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the
newsgroup so
all may benefit.

"inadmissible3" wrote in
message
...
Suzanne,

How do I do this StyleRef field?

Thank you.

"Suzanne S. Barnhill" wrote:

Alternatively, if the desired text appears in the document itself
and
the
field is formatted with a unique character style (which can be
identical
to
the Default Paragraph Font), a StyleRef field in the header will
pick up
the
text as it is replaced.

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the
newsgroup so
all may benefit.

"Jay Freedman" wrote in message
...
Ah, the light is starting to dawn...

What I suspect is happening is that Amicus Assembly does a
find-and-replace operation during the generation, looking for
things
surrounded by the %[ and ] markers and replacing them with data
according to the quoted name.

The problem is that headers and footers are in a separate area of
the
file (Word's technical term is "story") from the main text, and a
find-and-replace operation has to do some special work to find
things
in those other stories. (This is explained at
http://www.word.mvps.org/FAQs/Custom...ceAnywhere.htm.)
It
seems that Amicus Assembly doesn't do that extra work.

You might try bookmarking the scripts in the body text and using
cross-references to those bookmarks in the header. There's a
gotcha
there, as well, though: when Amicus Assembly replaces the scripts,
it
will probably overwrite and destroy the bookmarks (extra work is
required to keep them), and then the cross-references will show
error
messages to the effect that the bookmarks don't exist.

I don't think there's really anything you can do except complain
to
the company (Gavel & Gown Software) that their product lacks
functionality that you need. Send them the URL cited above, and
request an update.

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org

On Tue, 3 May 2005 12:11:07 -0700, "inadmissible3"
wrote:

Here is a sample of the script language that is from Amicus
Assembly-document
assembly program-

%[Matter.CustomField("Case Name")]
%[Matter.CustomField("County")] %[Matter.CustomField("Case No.")]

When this information is filled out when setting up the case
file,
and I
want to generate a document, this script language translates to
text
and
shows to the proper case name and case number in the document.
When
I do
this in the body of the document, it works fine, but when i copy
this
script
language inside the header/footer, it will not/does not show
anything
but
the
script language shown above.

Is there anything I can do? Thank you.
"Jay Freedman" wrote:

I'm sorry, but it still isn't making much sense to me, probably
because we're using the same words with different meanings.

Word has several classes of "fields", with many specific kinds
within
each class. These are the ones that seem to have the most
probable
connection to what you're doing:

- Plain "fields" are the class of fields created by the Insert

Field
dialog, or by pressing Ctrl+F9, or by a macro that contains an
ActiveDocument.Fields.Add statement. If you look in the Insert

Fields dialog, you'll see a couple of dozen kinds. Some that
might
be
used by your document creation program to display information
(like
case name and number) are the Quote field, the DocProperty
field,
the
DocVariable field, and the Reference field. Each kind of field
has
a
specific purpose, as described in Word's help file, but they
can
often
be "bent" to other purposes. Most fields of this class operate
perfectly well in headers/footers as easily as in regular body
text.

- "Form fields" are for use in a "protected form". The idea
here is
that you set up a document containing both static text and
changeable
fields; once the document is protected, the static text can't
be
selected or edited and only the fields are available. Word
prohibits
form fields in headers and footers -- so I suspect this is what
you're
trying to use.

- Controls in userforms (custom dialogs) are sometimes called
"fields"
although this is something of a misnomer. This isn't related at
all
to
your problem.

Then there are combinations of fields... If the document
generating
program is inserting form fields in the body of the (protected
form)
document, you can place a Reference field in the primary
(non-first-page) header to repeat that information. The form
field
has
a "bookmark name", which you can see in its Properties dialog;
the
Reference field needs to refer to that name. See part 2 of
http://gregmaxey.mvps.org/Repeating_Data.htm for illustrated
instructions.

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org

On Tue, 3 May 2005 10:05:07 -0700, "inadmissible3"
wrote:

Yes, I am using a document generating program whereby I have
fields
inserted
into a blank document that are populated by the information
found
in a
client
file. What i am attempting to do is to have the case name and
number
as a
header on the second page and every page thereafter. The
"script
fields"
polulate outside the header, but do not work within a
header/footer.
Make
sense?

Thank you again.

"Jay Freedman" wrote:

I suspect we're at cross purposes here about the meaning of
"script
language". I understood it to mean executable code that does
something, like
the VBscript or JavaScript that you can embed in an HTML
page.
Your
later
description indicates that it's text that should appear on a
(viewed
or
printed) Word document. In that case it has nothing to do
with
macros or
programming.

If your question is how to get the text to appear on the
second
and
subsequent pages but not on the first page, the answer is to
go
to
File
Page Setup, click the Layout tab, and check the box for
"Different
first
page". In the document, temporarily create a second page by
pressing
Ctrl+Enter at the end of page 1 to insert a page break. Open
the
header
area. If there is text in the First Page Header, remove it.
Place
the text
in the header on page 2. Close the header area, and delete
the
page
break.
Word will "remember" the header and display it on pages 2
and
beyond, when
the document becomes more than one page long.

This procedure is similar to the one described at
http://sbarnhill.mvps.org/wordfaqs/Letterhead.htm. The only
difference is
which header (First Page or the primary Header) you put the
text
into.

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org

inadmissible3 wrote:
The script language from a document assembly program is
like a
form
field that contains case name, number, etc. so when I want
to
generate a document to a particular client, and the
document
is
more
than one page in length, this information is in the
header/footer.

I have also posted the original question on the
programming
group
as
well, but if you have any suggestions, I will listen.

Thank you.

"Jay Freedman" wrote:

On Mon, 2 May 2005 17:53:01 -0700, "inadmissible3"
wrote:

I have inserted some script language from another
software
program
(Amicus Assembly) into and as a second (and subsequent)
page
header, but it doesn't work...

Thank you for your patience.......

inadmissible3

There's no reason to believe that script language from
any
other
program will work in Word. A Word document's header is
nothing at
all
like an HTML header except for the name.

You may need to reprogram the script as a VBA macro. What
is
it
supposed to do? In any case, it would be best to move the
discussion
to the programming newsgroup,




http://www.microsoft.com/office/comm... lang=en&cr=US.

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org