My OLE picture looks fine on screen but is clipped when printed.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am using a query and reptort to create name tags for guests. Each nametag
will have a picture corresponding to the individual's branch of service. The
pictures look great when they are on screen, but they are clipped on both the
left and top sides when printed. I have tried mutiple printers, and moving
the object to a different place on the report. Size for the object is set to
Zoom. An image that is static with every name tag does not have this
problem. Once again, the images look great when displayed on screen.
 
I am using a query and reptort to create
name tags for guests. Each nametag
will have a picture corresponding to the
individual's branch of service. The
pictures look great when they are on
screen, but they are clipped on both the
left and top sides when printed. I have
tried mutiple printers, and moving
the object to a different place on the
report. Size for the object is set to
Zoom. An image that is static with
every name tag does not have this
problem. Once again, the images
look great when displayed on screen.
Click to expand...

When you say "displayed on the screen", I don't know if you mean the Print
Preview of the badge with the picture, or something else. I don't use OLE
Objects and bound OLE Frames because of the bloat and reporting
difficulties. What you describe is not the way that Zoom is supposed to
work... it is supposed to fit the picture to the control in the largest
dimension and maintain the aspect ratio for the other dimension. If you
aren't talking about the Print Preview looking great on-screen, take a look
at the Control on the Report you are using to Print. In any case, perhaps
the following will be of help, and/or offer you a worthwhile alternative.

The sample imaging databases at http://accdevel.tripod.com illustrate three
approaches to handling images in Access, and the download includes an
article discussing considerations in choosing an approach. Two of the
approaches do not use OLE Objects and, thus, avoid the database bloat, and
some other problems, associated with images in OLE Objects.

If you are printing the images in reports, to avoid memory leakage, you
should also see MVP Stephen Lebans' http://www.lebans.com/printfailures.htm.
PrintFailure.zip is an Access97 MDB containing a report that fails during
the Access formatting process prior to being spooled to the Printer Driver.
This MDB also contains code showing how to convert the contents of the Image
control to a Bitmap file prior to printing. This helps alleviate the "Out of
Memory" error that can popup when printing image intensive reports.

Stephen, by the way, also has a picture/image control on his site that you
can use if the graphics filters are not available on the machine you are
using.

Larry Linson
Microsoft Access MVP
 
Larry,
Thank you for your reply. Upon reading your post and downloading and
studying the recommended website, it occurred to me that I am actually using
BLOBs I think. That is, I copied the image off of a public domain website,
and pasted them into a table. Wherever I pasted an image into the table, the
table just says "picture." The field type however was OLE Object.

The display I was referring to was the print preview screen. My nametags
look Wonderful in the print preview screen, but when printed, Every image is
clipped by about 1/8th of an inch on both the left and top sides of the
image. I am only using 20 different pictures that are not very large, and
memory does not appear to be an issue. Access doing its own thing when it
sends my report to the printer seems to be the issue, and as I do not
consider myself a VB guru, and I am trying to get this done very quickly, I
am wondering if there is a property setting or program or printer option I am
not aware of.

Thanks again for your reply.
 
Back
Top