Larry, Not much help, but I do know that : PRINT reportname WHERE whereclause ORDER BY orderby OPTION PRINTER |COLLATION ON |COPIES 2
Where reportname is a report that is 2 pages in length; will yield page 1, 2 then page 1, 2 again. With COLLATION OFF, you'll get page 1, page 1 then page 2, page 2. I've found the best way is to not have colored copies <g> But, if they must, you will have to determine the page count and warn the user to insert the appropriate number of colored sheets where appropriate. I can't seem to put my finger on it right now, but I think I remember something on the list about capturing the Page Set system variable on a two pass report...... Maybe it was a "it would be nice" thing, but I'll keep looking. Dawn -----Original Message----- From: Lawrence Lustig [mailto:[EMAIL PROTECTED] Sent: Friday, June 17, 2005 2:02 PM To: RBG7-L Mailing List Subject: [RBG7-L] - Printer collation issue. I have a difficult printer collation issue and I wonder if anyone has approached it. I am trying to print a bill of lading. I am printing on three part laser carbonless forms (pink/yellow/white). I will print a single bill at a time. These bills of lading often go over one page in length. I cannot predict how many detail lines will fit on each page, since the product description is a stretchable memo field and some descriptions are one line and other two lines. Finally, I want the three bills to print 'Customer Copy', 'Store Copy', and 'Office Copy' respectively. Got it? I could print the report three times in a row, changing a variable that is used to display the copy name. Unfortunately, since the paper is pre-stacked in the printer pink/yellow/white this does not work when the bill is two or more pages long. I noticed the extremely attractive COLLATION option in the help file. If I do this, I should (I assume, I haven't tried it) be able to print all the Page 1s (pink/yellow/white) then all the page 2s (pink/yellow/white) etc. The problem with this is I don't know how to change the name of the copy inside the report. I have a feeling it has to do with computing the page number in the page header, taking the modulus of the page number with respect to the number of copies, and use that as an index into an array of the copy names. Has anyone solved this problem already? -- Larry
