Pictures in Reports

  • Thread starter Thread starter Chris Grant
  • Start date Start date
C

Chris Grant

I have just set up a database and want to make a report
with picutres in them. I have made the query, with the
OLE object field named image, and then put it into a
report. However the report just displays a white box and
the file name of the image. Any help would be appreciated.
Best Regards
Chris Grant
 
Chris,

I usually leave the pictures in the file system somewhere
(c:\dbpics\pic1.bmp etc) and have a field in the table
with the full path and name of the associated picture.

In a report make sure the field with the path is in the
record source and on the report itself (set visible to NO
if it is not to be seen). Place an image control where you
want it on the report (you will need to point this control
at an image so just use any image file at this stage). In
the report section's on format event set the image
control's picture property with the required image path:

dim pic as string
pic = [picture path field name]
[imagename].Picture = pic

This is significantly different to what you are attempting
however I think to rectify your problem you will need to
do something during the "on format" period to get your
pictures to display correctly.

HTH

Terry
 
I have just set up a database and want
to make a report with picutres in them.
I have made the query, with the OLE
object field named image, and then put
it into a report. However the report just
displays a white box and the file name
of the image. Any help would be appreciated.
Click to expand...

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. When you use
OLE, you subject yourself to the limitations and restrictions imposed by
whatever imaging software is registered for the image file type on the
user's system -- and that is often not what you'd like.

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.
 
Back
Top