By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,650 Members | 1,976 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,650 IT Pros & Developers. It's quick & easy.

access 2007 will not print report

P: n/a
I have a DB that I developed on access XP (2002) and deployed over a
year ago. No one has had problems printing any of the reports within
the DB until we started loading 2007 on new computers. The access
2007 users cannot print one of the reports. This is maddening since I
cannot duplicate the issue on any computer that runs 2003 or below.

Is there something going on that I'm not seeing? Does anyone have any
suggestions at all on where I can start? TIA.

Snoopy33
Aug 28 '08 #1
Share this Question
Share on Google+
10 Replies


P: n/a
Suggestions:

1. Do they have a printer installed on their computers?
Access uses the metrics of the printer driver to calculate the layout of the
reports. If there is no printer (or if there is a problem with the driver),
Access won't be able to figure out the report.

2. Was the report designed and saved for "Default Printer" (File | Page
Setup, in report design view), or for a "Specific Printer"?

3. Is the database in a trusted location?
To trust your folder in the new version, click:

a.. Office Button (top left)
b.. Access Options (bottom of dialog)
c.. Trust Center (left)
d.. Trust Center Settings (button)
e.. Trusted Locations (left)
f.. Add new location (button)

4. Could there be a library reference problem with the A2007 machines?
More about references for the various versions:
http://allenbrowne.com/ser-38.html

5. Could there be an issue with permissions (e.g. if they don't have
adequate permissions to use the printer)?

6. Have they installed SP1 for Office 2007? If not, give them this link:
http://office.microsoft.com/search/r...11011033&CTT=5

Other general info re adapting to A2007:
http://allenbrowne.com/Access2007.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Snoopy33" <ho********@hotmail.comwrote in message
news:ff**********************************@m36g2000 hse.googlegroups.com...
>I have a DB that I developed on access XP (2002) and deployed over a
year ago. No one has had problems printing any of the reports within
the DB until we started loading 2007 on new computers. The access
2007 users cannot print one of the reports. This is maddening since I
cannot duplicate the issue on any computer that runs 2003 or below.

Is there something going on that I'm not seeing? Does anyone have any
suggestions at all on where I can start? TIA.

Snoopy33
Aug 28 '08 #2

P: n/a
Allen,

Thank you very much for the quick reply.

1. Do they have a printer installed on their computers?
Access uses the metrics of the printer driver to calculate the layout of the
reports. If there is no printer (or if there is a problem with the driver),
Access won't be able to figure out the report.
They have a network printer installed and are able to print anything
else. I currently have them printing the form
that contains the same information as the report (different format
than what we use but the info is still there), so i
don't think the problem is with the printer or driver.
2. Was the report designed and saved for "Default Printer" (File | Page
Setup, in report design view), or for a "Specific Printer"?
Yes, it was designed to use the default printer. It works fine for
everyone else. Currently about 10 to 15 users
using about 5 different printers. No one has issues with it other
than the 07 users/
3. Is the database in a trusted location?
To trust your folder in the new version, click:
* a.. Office Button (top left)
* b.. Access Options (bottom of dialog)
* c.. Trust Center (left)
* d.. Trust Center Settings (button)
* e.. Trusted Locations (left)
* f.. Add new location (button)
Using front end loader to save copy to local machine. Checked trust
center and the location wasn't included. Added it but it didn't
make any difference.

4. Could there be a library reference problem with the A2007 machines?
More about references for the various versions:
* *http://allenbrowne.com/ser-38.html
I checked this out. The only differences that i see is DAO 3.6 is
selected and not 12.0 access database engine. If i select this for
the DB
the next time that i make a change and their machines download the
changed DB won't it revert back to 3.6? Could this be what the proble
is?

>
5. Could there be an issue with permissions (e.g. if they don't have
adequate permissions to use the printer)?
As they can print in other applications and print other reports and
forms in the database I don't
believe this could be the issue.
6. Have they installed SP1 for Office 2007? If not, give them this link:
* *http://office.microsoft.com/search/r...C102486291033&...
That is the first thing that i tried.
While replying to this i checked a few other things out. First, If I
open the report from the DB Window, it opens fine into preview
window.
If I right click on the report and click Print, it will print.

I'm hiding my DB Window using an API Call and opening my form as
Modal / Pop Up. Is this what the proble is? Does access 07 have a
problem printing a report from a form set to Modal? I'm going to
further investigate this on my own and will post my results, but if
you have any insight in the mean time i'd appreciate it.


Thanks a million
Snoopy 33
Aug 28 '08 #3

P: n/a
Snoopy33 wrote:
Allen,
>>2. Was the report designed and saved for "Default Printer" (File | Page
Setup, in report design view), or for a "Specific Printer"?

Yes, it was designed to use the default printer. It works fine for
everyone else. Currently about 10 to 15 users
using about 5 different printers. No one has issues with it other
than the 07 users/
Can that person print any Access 2007 reports to that printer? IOW, is
the problem report specific or printer specific?
Aug 28 '08 #4

P: n/a
Ok,

I've removed the api call and the modal and pop up settings so that it
opens windowed. This didn't resolve the problem. It still
flashes up with a print dialog like it's spooling to the printer and
then it goes away without printing.

Now i'm really stumped
Aug 28 '08 #5

P: n/a
On Aug 28, 12:13*pm, Salad <o...@vinegar.comwrote:
Snoopy33 wrote:
Allen,
>2. Was the report designed and saved for "Default Printer" (File | Page
Setup, in report design view), or for a "Specific Printer"?
Yes, it was designed to use the default printer. *It works fine for
everyone else. *Currently about 10 to 15 users
using about 5 different printers. *No one has issues with it other
than the 07 users/

Can that person print any Access 2007 reports to that printer? *IOW, is
the problem report specific or printer specific?
The problem is definately report specific. I can print any report to
that printer accessing it from the DB window, but not through
VBA using docmd.openreport method

Aug 28 '08 #6

P: n/a
Snoopy33 wrote:
On Aug 28, 12:13 pm, Salad <o...@vinegar.comwrote:
>>Snoopy33 wrote:
>>>Allen,

2. Was the report designed and saved for "Default Printer" (File | Page
Setup, in report design view), or for a "Specific Printer"?
>>>Yes, it was designed to use the default printer. It works fine for
everyone else. Currently about 10 to 15 users
using about 5 different printers. No one has issues with it other
than the 07 users/

Can that person print any Access 2007 reports to that printer? IOW, is
the problem report specific or printer specific?


The problem is definately report specific. I can print any report to
that printer accessing it from the DB window, but not through
VBA using docmd.openreport method
I'd first import it into a new database and check it out. If that
doesn't fix it, maybe add a /decompile to the desktop icon command and
then recompile the thing. If that doesn't work, redo/rebuild it.
Aug 28 '08 #7

P: n/a
Thank you for your help

Aug 28 '08 #8

P: n/a
"Snoopy33" <ho********@hotmail.comwrote in message
news:75**********************************@f63g2000 hsf.googlegroups.com...
>
I've removed the api call and the modal and pop up settings so
that it opens windowed. This didn't resolve the problem. It still
flashes up with a print dialog like it's spooling to the printer and
then it goes away without printing.
To summarize so far:
- One specific report fails to print (or preview?) when opened with
DoCmd.OpenReport, but works when fired directly from the NavPane.

- This only happens in A2007 (even with SP1), but on several machines. Other
reports print fine on those machines.

- The problem occurs regardless of the window mode (normal or dialog), and
you tested this without hiding the main Access window.

You mentioned DAO 3.6. That's the correct library to use with an MDB; you
only use acedao with ACCDB format.

Presumably you have already tried stuff like a compact, decompile, compact
sequence, such as:
http://allenbrowne.com/recover.html
It might be worth recreating the report with SaveAsText/LoadFromText also
(link above), and setting minimal references.)

I'm also assuming we don't have multiple users opening the one database here
(i.e. each user has a separate front end.)

The next step would be to eliminate the things that could be affecting its
opening, e.g.:
- Is the report's FilterOnLoad property set to No?
- Is there anything in the report's Open or NoData events that could cancel
it?
- If there are subreports, temporarily remove them to see if the main report
opens.
- Set its HasModule property to No (after saving any code), an clear the
event properties of the report and its sections (particularly the Open,
Load, Activate, Resize, Filter, Timer events of the report, and the Format
and Print events of its sections.)

Especially, be suspicious of anything that reassigns the RecordSource of the
report and/or it's subreports.

If the problem persists, the next layer down is the source data:
RecordSource query, RowSource for controls, timing of the creation of any
temporary records, and so on.

Let's know if any of that is productive.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

Aug 29 '08 #9

P: n/a
Allen,

Give yourself a big fat raise!!! Thank you very much! You pointed
directly at the problem. The problem was definately with the Events.
Here's what I was doing wrong:

I have a module called (misleadingly) ReportFilterMDL with the
following code:

Public PartReportFilter As String
On my report i had the following code behind the on open event

If Len(PartReportFilter) 0 Then
Me.Filter = PartReportFilter
Me.FilterOn = True
PartReportFilter = vbNullString
End If
Everything would have been fine at that point, but my on click event
on my form had the following code behind it:

PartReportFilter = "ID = " & Me![id]

DoCmd.OpenReport "rptPrintPO",
acViewNormal, PartReportFilter

The code would have worked properly WITHOUT the on open events on the
report if it were:

DoCmd.OpenReport "rptPrintPO",
acViewNormal, , PartReportFilter

which would have pushed the string to the Where argument instead of
the Filter argument.
I guess Access 03 and < ignored the filtername in the code and used
the on open code of the report with no problem, but 07 couldn't make
sense of the code so it just stopped.

Removing the filter argument from the above code resolved the
problem. The report now prints fine on all work stations.

Thank you so very much Allen for taking your time to help me!!!!

Snoopy33
Aug 29 '08 #10

P: n/a
Excellent news!

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Snoopy33" <ho********@hotmail.comwrote in message
news:8c**********************************@e39g2000 hsf.googlegroups.com...
Allen,

Give yourself a big fat raise!!! Thank you very much! You pointed
directly at the problem. The problem was definately with the Events.
Aug 29 '08 #11

This discussion thread is closed

Replies have been disabled for this discussion.