Nicola, I have three options for you.
Option 1... Call the template twice. The first time would be to only show the proof for the customer to approve. The second time would create your imposed output file for the press. The difference in the output can be flagged by a field that we use called isProof and an unused body page. For your proof output this flag field would have a value of "yes", and that value would then trigger a rule in OnRecordStart to activate the unused page to compile. Once the card is approved, you create a duplicate instance file changing the value for isProof to "no". This then would not allow the unused page to compile and only the front would be compiled into the final imposition file. Option 2... Again, call the template twice. You can set the second page to contain the shell information already in the pdf template file. During your first call, make sure the "suppress static pdf background" box is unchecked to create a full two-page proof. The second time you compile the card after the customer's approval, make sure that same background box IS checked. This will print a blank for that page. When you impose your card, the second page may contain crop marks, but no images. Then simply remove that page, or only send page one, when making your plate. Option 3... This is the method that I actually prefer since what the customer actually sees is EXACTLY what will be printed - there is no chance for a glitch or hiccup to cause a different output to print on the final. I've been programming two templates for each job. The first would be the ProofTemplate that would create a hi-res pdf output. This proof file (given the name of the order number for this customer) is then stored off into an intermediate folder location. A low-res image can be created from this to display on the website for proofing purposes. Once the card is approved, a second data file is generated that only lists the order number (which is the same as the name of your proof pdf file) and the quantity. The proof card is then called into a FinalTemplate which simply pulls in the hi-res proof pdf file as a graphic - nothing changes within it. All the complicated creation rules were done in the ProofTemplate, so only the graphic rules are necessary to call in specific pdf pages. If you only wanted the first side of the card, then your FinalTemplate contains only one page and you can use the "pagenumber = xx" option filling in the specific page(s) from the proof pdf file. Good Luck, --- David A. Sweet Web Designer/Graphic Designer HKM Direct Market Communications A DirectConnectGroup Company No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.13.30/1029 - Release Date: 9/24/2007 7:09 PM +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Calling all FP Web Users! Do you have a question or lots of knowledge to share about FusionPro Web? If so, join our Printable Web to Print Users' Forum today! Send email to [EMAIL PROTECTED] to find out how! +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- -- Users of FusionPro Desktop have unlimited free email support. Contact Printable Support at [EMAIL PROTECTED] -- View FusionPro Knowledge Base, FusionPro Samples at www.printable.com/vdp/desktop.htm -- You are currently subscribed to fusionpro as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] -- -- Note: All e-mail sent to or from this address will be received or otherwise recorded by the e-mail recipients of this forum. It is subject to archival, monitoring or review by, and/or disclosure to someone other than the recipient. Our privacy policy is posted on www.printplanet.com --
