only one record prints

[kram]

I'm a new access user - I made a report to be able to
print out a series of records associated with a table, but
only one record prints out and then only a specific one.
It sound basic, but I can't figure out what I'm doing
wrong.

 

[Larry Linson]

I'm a new access user - I made a
report to be able to print out a series
of records associated with a table, but
only one record prints out and then
only a specific one.

"Made a report" isn't very specific. Perhaps you could clarify... what is
the RecordSource of your Report? If it is a Query, do you have Criteria? If
it is not, are you running the Report from a DoCmd.OpenReport that has
either a Flter argument or a WhereCondition argument? Are you running the
Report by choosing it from the list of Reports in the Database window, or
some other way?

Larry Linson
Microsoft Access MVP

 

[Tariq Bayzid]

-----Original Message-----


"Made a report" isn't very specific. Perhaps you could clarify... what is
the RecordSource of your Report? If it is a Query, do you have Criteria? If
it is not, are you running the Report from a DoCmd.OpenReport that has
either a Flter argument or a WhereCondition argument? Are you running the
Report by choosing it from the list of Reports in the Database window, or
some other way?

Larry Linson
Microsoft Access MVP

I have the exact oposite problem.
When i click the button i get all the record while i only
want the one selected. When i check the properties of the
eventprocedure i see the following.

Dim stDocName As String
stDocName = "Student Incident Sheet C&MD"
DoCmd.OpenReport stDocName, acNormal
Exit_Printer_Click:
Exit Sub
What i would like todo is that the report prints the
record i am on.
Any advice?
Thank you,
Tariq

 

[Larry Linson]

Yours is not the same problem, and yours is easy to handle:

Take a look at the WhereCondition argument of DoCmd.OpenReport, use the
unique id of the Record displayed in the Form to create a "WHERE clause
without the WHERE", and use that as the WhereCondition to run a report
showing just that one problem.

If your recordset were "huge" (many tens of thousands of records) it might
be worthwhile to expend a little more effort to create a complete SQL
statement to use as the RecordSource of the Report, but that is a little
more complex, and would be a subject for a different post.

Kram's problem appears to be the reverse... for some reason, he is ONLY
printing one record when he expects to priny them all.

Final advice: start a new thread with each new question. Don't post a
question as a followup to a new question. Many who answer questions here
only have time to look at questions to which no one has responded and
wouldn't have even seen this one. For other good suggestions on effective
use of newsgroups, visit the FAQ at
http://www.mvps.org/access/netiquette.htm.

Larry Linson
Microsoft Access MVP