How to make many 1pg rpts into multi page

[olichap]

I've got a report object/report form (CR 8.5, populated through VB6 app) which prints fine as a single print job. What I'm trying to do is combine multiple instances of the same report into one multi-page document/print job.

My users are essentially printing invoices, each of which is one page. If I can combine say 300 individual print jobs into one I no-longer have to worry about two peoples jobs getting mixed up.

I do use the CRVIEWERLibCtl.ReportSourceRouter in another part of the program to create a multipage report when displaying with the Viewer, and this works out fine. What I'd like to do is create a multipage report and send the job directly to the printer without any other user input. Some of these print jobs can be 700-800 pages long so I'd rather not require the user sit and wait to click on the Print button, if possible. If there is another way to add pages to an existing report object and then print, that'd be ideal.

Any ideas would be greatly appreciated.

Thanks,

Oli

 

[Ngolem]

just create another group based on Invoice number and make it Group #1

In the section expert enable "new page after" to make sure each invoice starts on a new page.

Your only other problem is to identify the invoices to be printed...is there a field in the database that indicates the invoice is ready for printing?? You also might specify which invoice dates might be printed....once you identify this you would put this criterai in a Record selection formula.



Jim Broadbent

 

[olichap]

I'm not sure I can utilize the "New Page After" logic in this case. I don't pass a recordset to the report. The report consists of many text boxes who's "Text" property I set based on the current record.

At the moment the app is only dealing with one invoice record's details at a time, populating the various text-boxes on the report, and sending it to the printer. I need some way to populate each single page report and then combine. Does it still sound like I can use "New Page After?"

Thanks,

O.

 

[Ngolem]

Hahaha...NOW, HOW AM I OR ANYONE ELSE GOING TO "MAGICALLY" GIVE YOU ANY ADVICE IF YOU DON'T TELL US HOW YOUR REPORT WORKS!!!

Just wasting my time...[shaking my head]

Put out details of how your report is built currently.

Unless you are feeding all of the information via parameters you are getting a record set somehow...even if it is for a single invoice.


Jim Broadbent

 

[synapsevampire]

It sounds like you need to build up the recordset (perhaps a temp table) first to allow for however many users you want to print for, and then issue the print.

-k

 

[olichap]

Jim I'm sorry if your time was wasted, but given my interpretation of my quandary I feel I explained the problem well enough without cataloging everything that transpires in my code and the report. I've an application that shells out 50-1000 print jobs and am looking for a mechanism to combine them into one (hence my discussion of the CRVIEWERLibCtl.ReportSourceRouter).

I could certainly change how the data is compiled, thus having a batch of complete recordsets with which to build my multiple pages. This would involve a significant re-write to a good bit of code, something I will be doing anyway but can't undertake at present.

So, back to my use of CRVIEWERLibCtl.ReportSourceRouter in an attempt to combine multiple report objects into one multipage object. This method will work but forces me to utilize the viewer. If there is a way to combine the objects and then send directly to the printer, that'd be ideal.

Thanks,

O.

 

[Ngolem]

sorry cannot help you there

Jim Broadbent

 

[Naith]

Olichap,

Can you break down how your report is populated? Basically, tell us which sections you're currently using for your report detail, what datasource you're connecting to, and how you pull the data back.

Cheers,

Naith