> One of the limitations of using the scheme for putting the
> CF code inside of the RTF is that you cannot put data into
> tables. I ran across the following tag in the gallery that
> takes care of this problem: CF_Query2RTFTable
This isn't true. I've used tables within RTF documents quite a bit, to even
include nested hierarchical relationships using the GROUP attribute of
CFOUTPUT within those tables. It's not exactly easy, though.
> Also, from a long-term maintenance and upgrade perspective,
> it's probably better to write your CF code in WORD and then
> save the file as an RTF file, which is then CFINCLUDED, rather
> than use STUDIO to edit the RTF code. You gotta be real careful
> about using <># characters in the WORD doc!
I'd strongly recommend using another word processing program instead of Word
for generating RTF; it generates the most verbose RTF possible, and that RTF
isn't always compatible with other word processors. I used to use
WordPerfect for this quite a bit. It generates much cleaner RTF, and places
each major RTF control word on a separate line, making it much easier to
read. I've been told that WordPad also does a better job.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
