--- Shari [EMAIL PROTECTED] wrote:
Jan,
That makes more sense. I've already made several of
the RTF files
with replacement variables embedded. Rev gets the
template, plugs in
its own variables, sets the RTFtext (and special
tabstops and print
size) of a fld to it (in a stack
--- Shari [EMAIL PROTECTED] wrote:
Jan,
They do not know how to do mail merge in Word. I
had originally set
this project up as an Excel spreadsheet which
exported info for
import into Word, but it was so convoluted and prone
to user error
(Excel doesn't have the power Rev does,
Jan,
That makes more sense. I've already made several of the RTF files
with replacement variables embedded. Rev gets the template, plugs in
its own variables, sets the RTFtext (and special tabstops and print
size) of a fld to it (in a stack specially made just for printing),
prints, and
Jan,
They do not know how to do mail merge in Word. I had originally set
this project up as an Excel spreadsheet which exported info for
import into Word, but it was so convoluted and prone to user error
(Excel doesn't have the power Rev does, especially with several
spreadsheets tying into
--- Shari Coxford [EMAIL PROTECTED]
wrote:
Figured out the wonkiness. It was related to
tabStops. They apparently are not pulled in
automatically with the RTF file so I did this:
Looked at the original RTF file and got the tabStops
in inches. Converted them to pixels (72 pixels per
Figured out the wonkiness. It was related to tabStops. They apparently are
not pulled in automatically with the RTF file so I did this:
Looked at the original RTF file and got the tabStops in inches. Converted them
to pixels (72 pixels per inch). Then just before printing, set the tabStops
