Max,
cool... thanks for the info. Can you share your cfml for this technique say
on a single field form/fdf file example. Im interested in your cfinclude
approach - im not getting that part - i understand the theory.
Not that I disagree with this approach - placing cf vars in the cfoutput
wrapped fdf file - but for what we were doing, and based on similar
debates - COM vs. edit text files, I came to the conlcusion with feedback
from Aymeric Grassart, that the COM object was a more "robust" approach.
This was important for us as our forms are 2-20 pages when combined, and
easily 200-300 fields per 2 pages.
Too much fdf code to go hunting thru on the fdf to find the location of the
vars vs. writing our own <cfscript>. I also feel that it will be easier to
maintain - long term. [long story....] Same old thing tho' - differnt
tools for different needs. If your forms are rather simple, Im confident
your method is way simpler, but where form design, layout and fields change
continuously - I prefer our appraoch - i feel like I have more control -
maybe I dont, but.....
Stephen M. Aylor
Aylor Insurance Agency, Inc.
"Specialized Insurance Programs for the IT Industry"
949.581.2333 vox
949.581.2333 fax
[EMAIL PROTECTED]
----- Original Message -----
From: "Max Paperno" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Monday, November 13, 2000 11:28 PM
Subject: Re: follow-up question to PDF [sample ActiveX]
>
> There is another way to do this without the ActiveX control. The FDF file
is a plain text file (with a fairly simple structure). Simply put in your
CF variables as the form field values (you can do this from inside Acrobat
even), wrap a CFOUTPUT around whole FDF file, then CFINCLUDE the FDF file
preceded by a CFCONTENT type="application/vnd.fdf". There is a /F switch at
the end of the FDF file which needs to specify a URL that points to the PDF
template. You can include any CF commands within the FDF file.
>
> I've never tried doing this using the COM object, but the above method
works great, doesn't depend on another component, and is cross-platform.
>
> Cheers,
> -Max
>
>
>
>
> >I have not tested the Adobe FDF ActiveX .... aka Adobe FDF Toolkit under
> >heavy loads, but its seems to work ok so far.
> >
> >http://partners.adobe.com/asn/developer/acrosdk/forms.html
> >
> >http://partners.adobe.com/asn/developer/acrosdk/DOCS/fdftkref.pdf
> >
> >Here's what we're doing with forms - so far .....
> >[kudos to Aymeric Grassart - of course]
> >
> >
> >1. Create your PDF document/form distill it/pdfwriter driver from word
> >etc.....
> >
> >2. Draw the "to be filled in form fields" on your pdf doc/form and assign
> >them properties
> >using the Adobe Acrobat full version form tool. There are other methods
> >that are kinda
> >interesting too - like scanning the doc from OmniForm4 and saving as a
PDF
> >:-)
> >
> >3. Inside Adobe Acrobat - full version - export FDF data (blank form
data)
> >to an FDF file on the webserver. This fdf will be used later as a
> >"template" FDF to be modified / filled in in your process.....
> >[myFirstFDF.fdf]
> >
> >4. Use <CFOBJECT> to call the tools in the FDF Toolkit activeX to pump
data
> >into your
> >your PDf Form/file from steps 1&2 above.
> <snip>
>
> --------------------------------------------------------------------------
----------------------
> Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
> Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send
a message with 'unsubscribe' in the body to
[EMAIL PROTECTED]
>
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
