Goal:  to have Sesame programmatically take a snapshot (image file format, pdf file format, ??) of a form on the screen, then save it to a filename (file name determined by a variable).

Payoff:  to print large batches of invoices, have the program differentiate paper printed invoices from those which should be emailed.  On the 'email' candidate invoices, Sbasic grabs the invoice # in the invoice# field, saves a FormView in an image file format (using that Invoice# variable to name the file; further programming will then automatically email the invoice file to the client).

PrintAFormToHTML  doesn't print correctly FormView Subforms that have been toggled to tableview, and as someone here pointed out, there are security issues with sending an html file as an invoice (file could be inadvertently(or not!) altered).   

If this supposed approach won't work, any other suggestions?  We have the potential to print/send 300 - 400 invoices via email each month .... too many to print each one manually to a pdf and then email manually.

Bharat,

Here is an example of my current invoices - http://www.wordcom.com/28441.jpg .  My customers like the easily viewed/easily found, colorful format. 

We generate/print invoices in batches - key in a string of sales order numbers; then the programming finds those sales orders and loops through, converting the sales order into the invoice format that you see in the example, prints it (PrintAForm); then changes the form back to SalesOrderVisual format; then loops on and repeats for the remainder of the string of sales orders.

We generate about 600 invoices a month (invoicing everyday for quick cashflow turnaround - thanks Sesame!), and could perhaps convert half of those to emailed instead of printed.  But I don't want to manually have to assign a pdf name to each invoice, then manually attach it to an email.  I want the invoicing programming to 'know' which invoices to email, grab the sales order # and 'print the invoice to a file (using the grabbed sales order # as the filename, then have Sesame programmatically attach that just-saved-file and email it to the client; then move on to the next invoice in the string to process.

That would offer tremendous time/money savings, and is a 'scale-up-with-no-additional-effort solution.

The programming is done, but the PrintAFormToHTML doesn't print correctly my SOLines subform from a formview toggled to Tableview (only prints the first record in form view).  And there's the security issue of the client being able to edit the html file.

So, regardless of the print command used, there isn't currently a way I know of to programmatically "print"/convert" the WYSIWYG form into a saved file (using a Sesame variable as the filename). 

Modified:  Actually, the product at this link http://www.converthtmltoimage.com/Usage.html  might be a good answer for having Sesame convert an html file to an image file and then email.  But it still leaves me with PrintAFormToHTML not printing converted-formview-to-tableview subform correctly.  So I'm still stumped.

Mark,

But I had something else to do this afternoon (LOL)!

That's an interesting angle (mostly parallel form to the same underlying database?).
   
So the invoicing would actually take place then using the parallel form .... Hmmm, so I just design an Invoice Form that links to the same Sales Order database fields  ... I'll  let my subconscious start planning this, and let you know how it's going.

Or else maybe just a parallel tableview SOLines2 form, using the underlying SOLines database fields, and then for invoicing purposes just make the SOLines subform (formview) Invisible, and the SOLines2 subform (tableview  form) visible, print, then revert and loop.

Thinking outloud - then I'd use PrintAFormToHTML to print the 'to be emailed' invoices from the InvoiceForm to a Invoice#.html filename, then have Seseame shell  out 'convertHTMLtoImage' command line conversion of that filename to an image file, then have Sesame email pickup the file and email it to the client.

That might work out.  Guess I know what I'm doing the rest of March!

Rick_R wrote on Mar 11^th, 2012 at 9:47pm:


PDF995 has a PDF995.ini file that has an entry: "Output File=". This allows you to automate the filenaming. I believe PDFCreator has something similar.

I had used PDF995 in the past, but started using free BullZip PDF printer a few years ago instead.  Link for info here: http://bullzip.com

From their features page:
============================
Features

    Print to PDF from almost any Windows program.
    Runs on Microsoft Windows 2000/XP/XP x64/2003/2003 x64/Vista/Vista x64/2008/Windows 7.
    Supports 64-bit operating systems.
    Direct output to the same file each time or prompt for destination.
    Control if the printer should ask if you want to see the resulting PDF document.
    Control output and prompts programmatically.
    Setup can run unattended.
    Graphical user interface.
    Password protect PDF documents.
    128/40 bit encryption.
    Quality settings (screen, printer, ebook, prepress).
    Set document properties.
    Watermark text, size, rotation, and transparency.
    Superimpose/background documents.
    Appending/prepending documents.
    User interface control.
    Command line interface to all settings.
    COM/ActiveX interface for programmatic control.
    Support for Citrix MetaFrame
    Support for Windows Terminal Server
    Multiple output types supported: BMP, JPEG, PCX, PDF, PNG, and TIFF.

The documentation was hard to find at first.  Here is an explanation: PDF Printer - User Guide

The Bullzip PDF Printer is a limited free edition of the PDF Writer from bioPDF. There are very little technical differences between the edition from bioPDF and the freeware version. This means that you can use the documentation for the PDF Writer at www.biopdf.com as long as you take into consideration that small differences may apply.
Here is a link to the documentation:  http://www.biopdf.com/guide/


This is the syntax for BullZip Print To File:
USAGE:
  printto "file name" ["printer name"]
------------------
Here's a link to the Command Line instructions with BullZip: http://www.biopdf.com/guide/examples/command_line/

==================
Edited:  Never mind.  I just checked my latest version and it no longer has the "printto.exe" file.  I had this in an older version of BullZip, and may be able to locate it for you, but no need because PDF995 will do it for you.  So, no optional program to offer you.  Good luck.

Thanks for the clue.  Will grab a copy for my toolbox.