View Single Post
  #34   Report Post  
Karen Hart
 
Posts: n/a
Default

Thank you again! What is ADDIN, and what is AFAIK? Since I am not an end
user (I am an MSAccess developer, extracting records from Access and
interfacing/merging with Word merge forms), maybe I will be interested :-)


"Peter Jamieson" wrote in message
...
Almost all of the available field codes are documented in Word Help,
usually near the bottom of the table of contents.The "=" field is usually
hardest to find if you search Word Help. Some field types such as ADDIN
are not documented (AFAIK) but are not usually useful for end users, and
others such as DATA are old field types that are typically updated
automatically by Word if you use them.

I never used WordPerfect very much but my understanding is that the way
data sources and the "merge code language" works in WP is more powerful
than the Word equivalents.

Peter Jamieson

"Karen Hart" wrote in message
news
That works beautifully! Thank you so much for all your help, and for your
very clear directions.

Is there anywhere I can read about such other wonderful secret codes
obtained by manually typing commands such as QUOTE between Ctrl-F9
brackets? I am wondering if all of the power and control of WordPerfect
merge codes is hiding in there somewhere!!! :-)

Thank you again, Peter!
Karen


"Peter Jamieson" wrote in message
...
In this case the date format switch needs to be applied to the DATE
field, not the QUOTE field, so try

{ QUOTE "{ DATE \@"MMMM DD, YYYY" }" }

If that does not work, can you let us know what you are seeing?

Peter Jamieson

"Karen Hart" wrote in message
ink.net...
Thank you so much, Peter! It works great, in the header, too! And your
directions are so clear :-)
The only thing I can't finess is how to make it print like March 25,
2005 instead of 3/25/05. I experimented with some variations of what
Graham wrote above, but I was unable to make it work. Can I impose on
you one more time for this final step?

"Peter Jamieson" wrote in message
...
It's an example of a "nested field". You can't usually enter them
easily using e.g. Insert|Field, so...

Use ctrl F9 to insert a pair of the special field braces {}

Type QUOTE "" in between to give you { QUOTE "" }

Put the insertion point between the "" and press ctrl-F9 to give you

{ QUOTE "{}" }

Type DATE between the inner {} to give you

{ QUOTE "{ DATE }" }

Peter Jamieson
"Karen Hart" wrote in message
ink.net...
Hello Peter,
I'm sorry I don't understand your reference below { QUOTE "{
DATE }" }
Is this a merge field I put in the merge form? If so, how do I
insert it?
Thank you,
Karen

"Peter Jamieson" wrote in message
...
How about

{ QUOTE "{ DATE }" }

?

Peter Jamieson

"Graham Mayor" wrote in message
...
This is not going to work That's what comes from not testing the
suggestions before posting.

Change the field back to a DATE field, update it, then merge to a
new
document
CTRL+A then CTRL+SHIFT+F9
will fix it.


--

Graham Mayor - Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org




Karen Hart wrote:
Thank you so much for replying, Graham. Coincidentally, I was on
your
web site checking it out exactly when your reply came :-) What a
cool web site! I love it! And I love that cute little thing that
follows my pointer around!

Anyway, once again, I tried...I insert this into the merge MAIN
document: {CREATEDATE \@ "MMMMd, yyyy" \* MERGEFORMAT}.

But sure enough, when I merge it, this is what I see:
August 24, 2000
(This is the date I originally created this merge source
document).
(Ctrl-A), (F9) is changing nothing, no matter if I do it before
and/or after merging.
Please help me out of the twilight zone!!

Thanks again,
Karen

"Graham Mayor" wrote in message
...
The date in the createdate in the merge source document is
irrelevant. If you merge to a new document the date that document
is
created becomes the createdate for that document. If the field
shows
the wrong date select all (CTRL+A) then update (F9). That should
fix
it.

--

Graham Mayor - Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org




Karen Hart wrote:
Graham,
I tried that and am getting a strange result. The resulting
merged
document is displaying the date the original merge form was
created...not the date the original merge form is being merged.
Does
that make sense? In other words, I changed the form document on
Jan.
14 and coded the date to be CREATEDATE. Now, every time the
form is
merged, the resulting date displayed is Jan. 14. What am I
doing
wrong?
Thank you.
Karen


"Graham Mayor" wrote in message
...
Use a CREATEDATE field for the date and merge to a new
document.
The new document will always show the date of the merge.

--

Graham Mayor - Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org




Karen Hart wrote:
How do I create a form file that upon merging inserts the
current
date of the merge, then does not update after that point? In
other
words, after the merge is complete, the resulting document's
date
field should be automatically unlinked. I do not want to
teach
the user to unlink the field with Ctrl-Shift-F9, because there
are
several of these date codes throughout the form file,
including
headers and footers, and also I don't want to risk that the
user
forgets to unlink the date field.

Thank you in advance.
Karen