Printing Reports

[MSUKevin]

Question for the masses:

I have a report that is exactly 1/2 of a normal 8.5 by 11 sheet of paper. What I want to do is have the report print itself twice on each sheet of paper.

The group I am building this database for have a receipt report that has to print 2 copies (1 for record-keeping and the other for the customer). They use paper that is perferated in the center for tearing.

Anyone know how to make Access 97' do this. It seems simple but I have yet to find the solution in help text or past posts on this forum.

All help is appreciated,
Kevin

 

[Fornatian]

Can you not just copy the entire report down again onto the bottom half of the report? Or is there is a problem doing this because of headers/groups?

Ian

PS. Alternatively you could ask them to literally break the page first then do two print-outs(brutal but effective)

 

[MSUKevin]

Ian,

Thanks for the reply. I can't do this because of the headers and groups like you stated. As far as breaking up the page first... I currently have the users doing this until I figure out a solution to get the report to print twice on the same page. This is a problem because the computer also has another program developed by an out-of-house client that prints reservation receipts twice on the same paper.

This becomes a hassle because the user has to switch paper between the pre-torn sheets and the full sheets. If you, or anyone else, has a idea on how I could fix this problem I am all ears

Thanks in advance,
Kevin

 

[Fornatian]

I haven' tried this so be warned that it may not work.

I wonder if you could add a subreport exactly the same to the bottom of the report and not set any parent/child links. Maybe it'll parse the group headers and footer the same.

Been away for a second just tried to insert a duplicate of the same report and it causes an error. BUT, When I copied the report from the DB window using cut and paste(so I now have two reports saved exactly the same, it WOULD allow me to drag and drop that report into the main report. Seems to work, but could be v. fiddly - but it may be an answer.

Ian

[This message has been edited by Fornatian (edited 09-06-2001).]

 

[Alexandre]

Just a thought, not tested but...
I would make a query1 selecting the field of the record source of your report, and afdding them a dummy column filled with 1.

Select[MyRecordSource].*, 1 AS Dummy
FROM [MyRecordSource];

And a similar query2 with a dummy column filled with 2. Then a union query to use as the new records source of the report:

SELECT [Field1], [Field2], [dummy]
FROM [query1]

UNION ALL SELECT [Field1], [Field2], [dummy]
FROM [query2];


Then introducing dummy as the first grouping level of your report should do the work, although it may not be the most efficient method.

Alex


(the Sql for the union query was dubious...)

[This message has been edited by Alexandre (edited 09-06-2001).]

 

[Alexandre]

Sorry, just re-thinking about it and I realized that it would duplicate your reports, but not on the same page

Alex

[This message has been edited by Alexandre (edited 09-06-2001).]

 

[Alexandre]

[This message has been edited by Alexandre (edited 09-06-2001).]

 

[MSUKevin]

Thanks to everyone for the replys but I still haven't found the solution.

Pat, in regards to your suggestion of using the label wizard to create the report, the problem I have run inon is that the report is generated by the SELECT DISTRINCT ROW funciton so that it only pulls the current record viewed on the form. When I go into label wizard to try and use your suggestion it tells me that I cannot proceed without chosing a table or query for which the report will be based.

Do you, or anyone else, have an idea on how to get around this?

I have also tried all the different suggestions by other who have posted on this topic but I have not had any success.

Ian, I tried to copy/paste a copy of the report from the db window into the report but it only let me put the info on top of the other set of the same info... (very confusing I know!)

If any of you good people would be interested in taking a look first hand at what I'm working with please let me know and I can send you a copy.(The file is small)

Any other suggestions?

Thanks in advance for all your help I really appreciate it!

Kevin

 

[R. Hicks]

If the report only takes 1/2 of the physical size of the sheet (including the margins) to print then try this:

Make a new table, add one field (name doesn't matter) you can leave it to text datatype.
Close and save this new table.

Open the new table and place 2 records in this table.
(You can enter 1 and 2 for the values, again it doesn't matter)

Now add this new table to the Record Source query that the report is bound to. Do not add any Joins to this table. You do not have to add the field to the recordset, only the table.

The addition of this table containing 2 records will cause the report to generate each record twice in the Recordset, thus .... 2 copies.

HTH
RDH

[This message has been edited by R. Hicks (edited 09-07-2001).]

 

[MSUKevin]

Pat and R.Hicks,

Thanks for the replys I really appreciate it. I think you both are talking about the same idea with the dummy table with two records. My problem is that I don't have the report being generated through a query but instead have it linked through the record sources by the SELECT DISTINCTROW func. Is this bad practice?

The reason I was linking the report directly to the form the information is generated from is because I wanted to have the report show only the individual record, and not all of them on each receipt. the code I have on the print cmd button is as follows:

Private Sub Command54_Click()
On Error GoTo Err_Command54_Click

DoCmd.OpenReport "Receipt", acViewNormal, , "[PrintID] = " & Me![printID]

Exit_Command54_Click:
Exit Sub

Err_Command54_Click:
MsgBox Err.Description
Resume Exit_Command54_Click
End Sub

Is there a "gentle" way I can transfer this info to a query so that I can follow your suggestions, while still making the cmd button only pull information for the selected record?

Please help if you have the time.
Thanks for all your assistance,
Kevin

 

[MSUKevin]

Pat, thanks for the tip! I got it to work by doing what you suggested. I just wanted to say thank you to everyone who has helped me out with this problem by posting on this thread.

I sincerely appreciate the time and effort each of you has put in to helping out someone, (read: me), with less knowledge on this subject!

Thanks again

Kevin