Like it says ... on *some* PCs (all are WinXP SP2 w/ Office 2003 SP3) when creating a snapshot file the file gets stretched ...
The report is set up to print in landscape and it looks like the snapshot is stretching what would appear if the report was set up as portrait into a landscape orientation and width so what should print as 1 page gets stretched so the second page has the last three columns of my report.
In the past I have had problems with previewing reports directly in Access so my workaround is to always opena report hidden, close it and they display it in preview for users ... this works perfectly. I am guessing that once again the Access team is not paying attention to printing issues and have royally screwed up as the native Access report not only displays correctly but also prints correctly ... it just can manage to output to sanpshot correctly.
If anyone has experience (or even an educated guess) besides chnagin to a different printer / print driver (I am in a lrge corporation and that ain't gonna happen any time soon as Access is the only app that has a problem) I would appreciate you posting up for me :-)
TIA,
Steve
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
we see this all the time...
the only solution I've come up with is to share the printer that will be printing the snp, set the page properties of the printer, use specific printer option with the shared printer on the page setup in report design and export.
Machines using the snp will also need to have all fonts used in the report as well as snps don't embed fonts.
Thanks for the input ... sigh ... I didn't think it would be an easy fix (but I was hoping it was anyway). Unfortunately I can not "assign" a specific printer as some of my apps are used by multiple departments. I guess I will try seeing if outputting the snapshot twice fixes anything, kind of like I am already doing for regular reports, although I doubt it as the docmd.outputto takes the name of the object (and not the object itslef) so my guess is that it spawns a seperate report object (and hence my work around for report preview issues gets foiled) and then does the output rather than being able to take what is actually, already being displayed ...
I'll keep thinking on this and post back if I find anything of value.
Thanks again,
Steve
Business Accounts
Answer for Membership
by: kelvinsparksPosted on 2008-05-31 at 00:08:21ID: 21682957
In my experience snapshots are not a snapshot.
I had a client where the ouput reports had to precisely sized. Snapshots failed & in the end we had to code up to use pdfs. That was in A97 days.
Thanfully Access 2007 had a built in pdf generator, which I think is an admission that snapshots weren't successful.