Report as Snapview picking up default printer settings

[JanMar]

I have an Access 2000 backend db with a frontend 2000 mde db.
Reports printing to a user selected printer are picking up the print
settings (paper width and length) from the PC's default printer. So a report
that should be printing on A4 is printing in the top left hand corner in
about 10cm * 10 cm over several pages, the same size of the labels.
The application prints labels to the default printer (usually a Zebra with 1
label on a continuous roll). It also prints several reports in preview with
the printer dialogue box for the user to choose which printer for the report,
using this code.

DoCmd.OpenReport sWhichReport, acViewPreview, sOpenArgs 'Open the report
with query name as filter in preview
DoCmd.RunCommand acCmdPrint
DoCmd.Close acReport, sWhichReport, acSaveNo 'Close the report

The reports have Page Setup Default Printer selected.

After reading posts on this site I removed the Track name AutoCorrect option
from the backend, but did not create a new db and import the tables. (the
front end did not have it selected).

Several clients with Access 2003 print the labels successfully, print a
manifest report to a selected printer on A4 correctly, then send a snp file
of another report using the following code.

DoCmd.OutputTo acOutputReport, "rptConnote", acFormatSNP, MailAttach
'Print to file SnapViewer
DoCmd.Close acReport, "rptConnote", acSaveNo

The snp file should be A4 size, but it prints to the top left hand corner
about 10*10cm. If this same report is printed to a printer it will print
correctly on A4.

What am I missing?

--
JanMar

[Peter Yang [MSFT]]

Hello JanMar,

I understand that some clients cannot print report properly. It prompts for
printer dialog and sometimes cannot print to the A4 but 10cm * 10 cm in top
left corner of the page.

To isolate the issue, you may want to check if the issue occurs on a
different database or sample northwind database. If the issue only occurs
on this specific database, it might be a corruption issue. You may want to
import a report and related tables to a blank new database to test the
situation.

If the problem only occurs with some clients, you may try to create a new
user and log on as the user to see if it is related user profile.

You may also want to change the default printer to a different printer or
MS Office image writer to see if it is printer related problem.

If you have any update, please feel free to let me know. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[JanMar]

Thank you for your reply.

The report prints Ok if it is actually printed to paper. However if the
user chooses to email the report it is output as a Snap file using - (and the
default printer would be set to the label printer at this time)

DoCmd.OutputTo acOutputReport, "rptConnote", acFormatSNP, MailAttach

DoCmd.Close acReport, "rptConnote", acSaveNo

In this case the contents of the snp file will look as though it was using
the label printer settings ie, what would have print on an A4 sheet will be
spread over 5 pages in huge font with only the top half of the normal
contents of the page. However if the same report was printed to a printer it
would be fine.

I cannot duplicate the problem on the development machine.

--
JanMar

[Peter Yang [MSFT]]

Hello,

I'd like to confirm if the default printer of the user is changed to label
printer automatically when you run the code to export the report?

If not, you may want to change the default printer to a different one such
MS Office image writer to see if makes any difference.

By design, the snapshot viewer should inherit the resolution from the
report that the snapshot was created from. By default, the report should
take the resolution from the default printer (if no other printer was
specified for the report.) Also, it may use the maximumn resolution of the
default printer though the resolution is set to a smaller one. I think this
might be the cause of the issue.

If the issue persists, you may want to change the default printer by code
before your code and change it back after the code to test the situation:

208840 How to use code to change a report's printer in Access 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;208840

Please let's know if you have any further questions on the isuse. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA

Microsoft Online Partner Support

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

======================================================

[Peter Yang [MSFT]]

Hello,

I'm still interested in this issue. If you have any comments or questions,
please feel free to let's know. I look forward to hearing from you.

[JanMar]

Well, obviously that was a silly idea of mine, of course, then the report
will print, which I don't want to do. However the snp file was correct.
Any ideas?
The problem occurs when the default printer is a label printer (or does not
have A4 capability). The OutputTo acOutputReport acFormatSNP inherits its
properties from the default printer.
This is the line of code

DoCmd.OutputTo acOutputReport, "rptConnote",
acFormatSNP, MailAttach 'Print to file SnapViewer

Thank you.
--
JanMar

"JanMar" wrote:

> Thank you for your interest.
>
> No I haven't solved the problem, I think you are right to suggest that
> Snapshot is inheriting the settings from the default printer, in this case a
> label printer.
>
> I am going to try asking for the printer as if the report was going to print.

> --
> JanMar
>
>
> "Peter Yang [MSFT]" wrote:
>

[Peter Yang [MSFT]]

Hello,

Did you try to change default printer settings before you export to
snapview and change it back afterwards? You may want to refer to the
following articles for reference:

Programming Printer Settings in Microsoft Access 2002
http://msdn2.microsoft.com/en-us/library/aa139946(office.10).aspx

208840 How to use code to change a report's printer in Access 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;208840

If you have any update, please feel free to let's know. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

[Peter Yang [MSFT]]

Hello JanMar,

To package and deploy a runtime version of Access XP or 2000, you would
need the corresponding Developers Edition of Office. If it’s only the
backend that you are distributing (i.e. an mdb file), this might not be
necessary. As long as Jet is properly installed on the machine, Access is
not required to use the runtime. If the machines do not have the current
version of Jet installed, follow this step:
<http://support.microsoft.com/kb/239114/>
and then the below step:
<http://support.microsoft.com/kb/271908/en-us>

This will get the latest version of Jet and MDAC installed on the
machine(s).

It's possible that the runtime version could work on Windows 98. However,
please note that the support for Windows 98 and ME has been retired
effective July 11th 2006 and we strongly encourage all customers to move to
a current operating system, as no further security updates will be
available for Windows 98 or ME. Also, the mainstream support for Office XP
and 2000 has also been retired effective July 11th 2006.

For more information on Support Lifecycle by product, please visit:
<http://support.microsoft.com/gp/lifeselectindex>

Please feel free to let me know if you have any questions.