Reports problems - converted from 2000 to 2002
John Lawrence
All reports show to be directed to Default Printer. The
same MDE runs fine on any PC not upgraded to Access 2002.
The only workaround I've been able to give my users is to
preview the reports first, then assign the printer they
want thru the "Print..." dialogue.
Further assistance would be immensely appreciated!
Thanks,
John Lawrence
>-----Original Message-----
>Hi John,
>
>Tom has addressed the point in his post. You can try it
and let me know if this
>solves your problem or if you would like further
assistance.
>
>Sincerely,
>
>Simon Liao
>Microsoft Support
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>Get Secure! - www.microsoft.com/security
>
>
>.
>
Peter Cosacchi [MS]
Is the behavior limited to a particular MDE? Only particular reports? As
a test, try building an MDE from the Northwind sample database and see if
those reports still target your printer on the other machines.
There was no major change between Access 2000 and Access 2002 in how it
handled printer settings. Do you have any code in your MDE that uses the
PrtDevNames or PrtDevMode propeties?
Another workaround would be to force the report to use a particular printer
at runtime, as per Q208840, manipulating the reports Printer object:
Private Sub Command0_Click()
DoCmd.OpenReport "<name of report>", acViewPreview
Reports("<name of report>").Printer = Application.Printers("<name of
printer>")
DoCmd.Save acReport, "Catalog"
End Sub
This would require that you new the printer that each user would be using.
Peter Cosacchi
Microsoft Support
--------------------
| Content-Class: urn:content-classes:message
| From: "John Lawrence" <john.l...@nana-colt.com>
| Sender: "John Lawrence" <john.l...@nana-colt.com>
| References: <d76801c269b7$be56b3c0$37ef2ecf@TKMSFTNGXA13>
<2LGkHGeaCHA.1496@cpmsftngxa09>
| Subject: RE: Reports problems - converted from 2000 to 2002
| Date: Thu, 3 Oct 2002 12:00:45 -0700
| Lines: 32
| Message-ID: <f31301c26b0f$2d8f1b30$37ef2ecf@TKMSFTNGXA13>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcJrDy2Pu2Ab0uVeSdudw1SRDupdvQ==
| Newsgroups: microsoft.public.access.reports
| NNTP-Posting-Host: TKMSFTNGXA13 10.201.226.41
| Path: cpmsftngxa06!cpmsftngxa10!cpmsftngxa09
| Xref: cpmsftngxa06 microsoft.public.access.reports:89322
| X-Tomcat-NG: microsoft.public.access.reports
John Lawrence
No, I just created a simple mdb with a sample table in it
and a basic report. On the users machine the report opens
in design & print preview just fine, but even tho "use
default printer" was selected, the printer it wants to
print to is the one in my office, when it should default
to the users local default printer. This only occurs on
users upgraded to Office/ACCESS XP. The users with 2000 or
no ACCESS at all run the MDB/MDE's just fine as always.
In instances where the user can preview the report, they
can change the printer to whatever they want, but this is
very impractical to make them do for every report. Also, I
am aware I can hardcode in a printer designation, but with
a distributed MDE who knows where it's used? Not an option.
There's no code like PrtDevNames or PrtDevMode in any
module, I've only let the default settings handle any of
that. I'm stumped, any help you can give would be greatly
appreciated.
Thanks,
John Lawrence
Systems Analyst/Programmer
NANA/Colt LLC
john.l...@nana-colt.com
>.
>
Peter Cosacchi [MS]
To further isolate the problem, here are some other questions.
1. Is Access the only app having the problem (ie, can
Word/Excel/Powerpoint documents print ok on the target machines)?
2. What happens if you build the Northwind sample database into an MDE and
distribute it (since you did not design those reports, they should not
inherit your printer info)?
3. What OS is involved with the clients? Do they all have the same
operating system, or different?
4. Same behavior printing Forms, or only reports?
5. Is the MDE shared, or are you physically locating the file on each
machine?
I've looked into the issue some more, and did find some similar cases. The
most common fix was to open the report on the target machine, select a
specific printer, close and save the report, then open it again and select
the default printer. In most of the cases, that seemed to do the trick in
resetting the correct default printer.
Peter Cosacchi
Microsoft Support
--------------------
| Content-Class: urn:content-classes:message
| From: "John Lawrence" <john.l...@nana-colt.com>
| Sender: "John Lawrence" <john.l...@nana-colt.com>
| References: <d76801c269b7$be56b3c0$37ef2ecf@TKMSFTNGXA13>
<2LGkHGeaCHA.1496@cpmsftngxa09>
<f31301c26b0f$2d8f1b30$37ef2ecf@TKMSFTNGXA13>
<wuzRqa#aCHA.2344@cpmsftngxa06>
| Subject: RE: Reports problems - converted from 2000 to 2002
| Date: Wed, 9 Oct 2002 12:32:31 -0700
| Lines: 126
| Message-ID: <5bf301c26fca$9c03d910$39ef2ecf@TKMSFTNGXA08>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcJvypwDnpZHAOFMQzq6s0E/QIvQ3Q==
| Newsgroups: microsoft.public.access.reports
| Path: cpmsftngxa06
| Xref: cpmsftngxa06 microsoft.public.access.reports:89837
| NNTP-Posting-Host: TKMSFTNGXA08 10.201.226.36
| X-Tomcat-NG: microsoft.public.access.reports
John Lawrence
ACCESS is the only app having this problem.
I did convert Northwind into 2002 format and made an MDE
of it, then copied both the MDE & MDB files onto the
target machine. From the target, I ran the MDB. From the
Database view, selecting the File/Print menu option I see
the users default printer.
On selecting a Form, print,page setup or preview gives the
error "There was a problem retrieving printer information
for this object. The object may have been sent to a
printer that is unavailable". I open the form in design
view, go to File/Page setup, select "use specific
printer", then select "use default printer". That toggling
of the default printer option works - the form previews
and prints.
On selecting a Report I cannot print,preview or even open
the report in design view. Period. Since I never used
Northwind on my production PC, even selecting my own
printer as default has no effect. On the MDB/MDE files I
have been creating I can at least open the report in
preview mode, then select the printer (or toggle the
default setting as on a form) and the report prints. But
that must be done for each report, and I cannot burden my
users with that task. And not all Reports are available
(from my interface) for preview anyway.
We are using Windows 2000 as an OS.
Each distributed MDE (as a front-end)is locally installed
on each users machine, sharing a common database located
on a server (back-end).
If I cannot find an equitable resolution to this issue we
will have to uninstall Office XP from all our machines
(including my own production PC) and reinstall Office
2000, which had none of these problems. I'm hoping we can
fix this before we resort to that. I do appreciate your
help in this, and eagerly await a solution.
Thank you very much.
John Lawrence
Systems Analyst/Programmer
NANA/Colt LLC
john.l...@nana-colt.com
>.
>
Peter Cosacchi [MS]
What is the OS on the target machines? How many machines are affected?
Is the behavior consistent among ALL Access 2002 desktops, or do some
Access 2002 desktops handle the reports fine?
One workaround would be to programatically open the object in design view,
toggle the printer to a specific printer and then the dummy printer, then
close and save the report. If you could build a function that did that
through code, you could tie that function to a 'RunOnce' procedure whenever
the MDE is first run on a machine. That would at least shield your users
from having to manually flip the default printer.
Check out this link for resources on programatically manipulating the
printer for an object:
http://www.microsoft.com/AccessDev/Articles/GetzCh10.HTM
Peter Cosacchi
Microsoft Support
--------------------
| Content-Class: urn:content-classes:message
| From: "John Lawrence" <john.l...@nana-colt.com>
| Sender: "John Lawrence" <john.l...@nana-colt.com>
| References: <d76801c269b7$be56b3c0$37ef2ecf@TKMSFTNGXA13>
<2LGkHGeaCHA.1496@cpmsftngxa09>
<f31301c26b0f$2d8f1b30$37ef2ecf@TKMSFTNGXA13>
<wuzRqa#aCHA.2344@cpmsftngxa06>
<5bf301c26fca$9c03d910$39ef2ecf@TKMSFTNGXA08>
<OR9kiT#bCHA.1904@cpmsftngxa06>
| Subject: RE: Reports problems - converted from 2000 to 2002
| Date: Thu, 10 Oct 2002 15:51:17 -0700
| Lines: 260
| Message-ID: <119901c270af$8b0ce120$36ef2ecf@tkmsftngxa12>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcJwr4sM+skMHuuYRAWSvbeSiur5lg==
| Newsgroups: microsoft.public.access.reports
| NNTP-Posting-Host: TKMSFTNGXA12 10.201.226.40
| Path: cpmsftngxa06!cpmsftngxa08!cpmsftngxa09
| Xref: cpmsftngxa06 microsoft.public.access.reports:89978
| X-Tomcat-NG: microsoft.public.access.reports
John Lawrence
We are using Win 2k as an OS all the way around. There was
about 8 machines affected, and I also distribute apps
outside of our company to other clients. We have a little
over 300 workstations total. Every PC that had Access 2002
had this problem. The machines without Access at all or
that have Access 2000 printed fine.
I've thought about using that code as a workaround,
however I'm not sure if an MDE file will allow saving it
(the report) or I'd have to run the code each time a
report is run.
It would have been pretty much my only option, had we not
made the decision yesterday to discontinue upgrading any
more machines to Office XP. We reinstalled Office 2000 and
every machine is back to normal. It's managements'
viewpoint that we stay with Office 2000 in the long term,
until some earth-shattering-have-to-have-it improvement
comes along in the next version of Office. I have kept a
production PC loaded with Office XP in case I do find a
real solution to this issue.
I appreciate your time and effort, but I cannot (will not)
write code like that to make the product perform as it was
intended. I'm looking for a solution. I've done about all
I can do - if it doesn't use the default printer as I've
asked it to... What else is there? Anyway, again thanks,
and any help you can give is greatly appreciated.