Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Saving printing properties

edited January 2002 in General
Hi,

I have to save the printer properties of each report. What should I save
exactly so that i can easily change a reports printer and who could i save
that? Is it possible to do that in an mssql dbase?

Also is it possible to let a report print to a printerque? Our customer
wants to save the printer names of each record so that not every time a
question has to come for which printer should be printing a report.

True I could set saveprinterdialog to true but that's not their desire.
They want 1 form that has the names of all the reports in column 1 and the
printer names in column 2..

Could somebody help me? I have no idea how to finalize this.

regards
Thomas Los

Comments

  • edited January 2002
    Create a lookup ReportPrinterSetup table. Then copy the Report.PrinterSetup
    object's properties to the db table.

    Each time you print a report, it creates a separate print job and it is
    placed on the print spool. We don't have any way to write them to a spool
    file, so that they can all be printed at once. The only way multiple reports
    can be printed as one report, is to place each report inside of one single
    report, as Section style subreports.

    You could dynamically build multiple reports, one for each printer. Then as
    the user matches a report to a printer, you can create a section style
    subreports in the appropriate report. Then load the selected report into the
    subreport. Then when the user chooses to print, then you can send the
    single reports to its associated printer.


    Cheers,

    Jim Bennett
    Digital Metaphors


This discussion has been closed.