Well, yeah, you can always *try* to pull an Abort on it, sure.  But as I said, if the
pages are already spitting, the odds are that most/all of the bits have already
spooled.  To get an idea of how to send an Abort, see
http://vb.mvps.org/samples/PrnInfo -- in particular, the following methods of the
CPrinterJobs class:

  Public Function ControlCancel(ByVal JobId As Long) As Boolean
     Dim os As OSVERSIONINFO
     ' NT4 is the dividing line between two different
     ' control codes for this call.
     os.dwOSVersionInfoSize = Len(os)
     Call GetVersionEx(os)
     ' Attempt to cancel passed job.
     If os.dwPlatformId = VER_PLATFORM_WIN32_NT And os.dwMajorVersion >= 4 Then
        ControlCancel = SendControl(JobId, jcDelete)
     Else
        ControlCancel = SendControl(JobId, jcCancel)
     End If
  End Function

  Private Function SendControl(ByVal JobId As Long, ByVal ControlCode As
JobControlCodes) As Boolean
     Dim hPrn As Long
     ' Get handle to printer.
     Call OpenPrinter(m_DevName, hPrn, ByVal 0&)
     If hPrn Then
        ' Send requested control code.
        SendControl = CBool(SetJob(hPrn, JobId, 0, ByVal 0&, ControlCode))
        Call ClosePrinter(hPrn)
        ' Update all object data.
        Call Me.Refresh
     End If
  End Function

That will, at least, stop Windows from sending any more bits down the wire.  What's
already in the printer's internal buffer is out of reach, however.

Good luck...   Karl

Even via Control Panel or the Printer dialog (double-clicking the print icon
in the systray, and these might even be one-in-the-same), you can only abort
what hasn't already been fed to the printer.  If you're printing a large
document, it might be entirely spooled, but Windows is feeding it to the
printer in the background.  At what point you can abort printing, if you can
at all, depends on the printer itself (i.e. how much memory it has).

As far as VB, it only lets you abort if you're still spooling (i.e., there's
been no Printer.EndDoc).  You might be able to use the AbortPrinter Win32API
function to abort a print job that you've "completed" in VB (IOW, you've
executed Printer.EndDoc), but even then, only what *hasn't* been sent to the
printer already would get aborted.  Also, this would depend on whether
spooling and background printing is enabled (and possibly even other printer
settings supported by any given printer).

Hi Anne --

Hey, that'd be great!  If you'd also like to display banner(s), take a look at
http://classicvb.org/#Banners (others are also available, if none of those work!)

Btw, we had some "server issues" with signatures last week.  If you hear of anyone
that says they tried but were rejected, please urge them to take another shot at it.
I'm fairly certain the problem was resolved.

Thanks...   Karl