Hi Afix,

   You are welcome! 

   To answer your question: the e-mail will be sent if the list of e-mail addressees (TO and/or CC) is not empty. If both the "TO" and "CC" lists are empty, than nothing is sent. Please note that the sample VBA code has the e-mail section commented out. Therefore, if you had already preset an e-mail when you setup the Batch printer in the program, than that e-mail would always be sent unless you override the settings in VBA.

   The way to think about it is: changing the settings with the VBA code is the same as making the changes manually through the user interface.

    The action option is done when you decide to print. Therefore, to summarize:

    1. Get the settings
    2. Change them as required
    3. Save the settings
    4. Print to the Batch printer (which will use the settings you set at step 2)
    5. Batch printer does it's magic, including sending the e-mail(s)

    The comment about sending it manually is true. It would give you better control. I went back to the sample code, and I see that I put the code for the manual FTP upload, but that I forgot to add the manual e-mail code which would allow you to e-mail the PDF manually after it has been created. My fault (sort of). I can add the SMTP e-mail function fairly easily, but the MAPI e-mail will require more work (but it is not impossible).

    Another way to ensure that the flow goes well would be to turn on the progress window, and then look for that printer window which will be displayed while the e-mails are being sent. Once the printer window disappears, then it would be safe to print and send the next e-mail. Basically, you would have to use the "FindWindow" API call:

Private Declare Function FindWindow Lib "user32" Alias "FindWindowA" (ByVal lpClassName As String, ByVal lpWindowName As String) As Long

    then, in the VBA Code:

    'Search for the BatchPDF window
    Do
        WinWnd = FindWindow(vbNullString, MyBatchPrinter)
        DoEvents
    Loop While WinWnd <> 0
    ' Batch Printer Window is now closed
    ... continue here

    Of course, HUGE WARNING, in that the code above will set yourself up for an infinite loop, so you'll want to setup a timer or a counter so that your program gives up after X minutes. I've added the Do Events so that at least you can pause the code and quit without having to force the application down.

   I hope that helps!