Displaying Multiple photos on report

[Rich]

Hi,

Have a Access 2003 db and want to display more than one photo/picture on
a report. Have a table of people, each with an id. Have another table
linked to the first with no or as many photos linked to the ID from the
first table.

Would like to print a report for an ID with all of the associated photos
for that ID.

I use the MS help for displaying images and that is fine, except it
displays the first photo for each photo record for the ID.

Can't find an appropriate Event item to get this to display the correct
photo for anything past the 1st.

Also should note that I have attached the photo record report as a
sub-report (which has the MS image display code) embedded in the main
report. If I display it one record at a time, the photos change, but if
I view them as a continuous forms, they are all displayed as the first
photo.


I hope that makes sense.

Help is much appreciated.

Thanks,
Rich

 

[Larry Linson]

Hi,

Have a Access 2003 db and want to display more than one photo/picture on a
report. Have a table of people, each with an id. Have another table
linked to the first with no or as many photos linked to the ID from the
first table.

Would like to print a report for an ID with all of the associated photos
for that ID.

I use the MS help for displaying images and that is fine, except it
displays the first photo for each photo record for the ID.

Can't find an appropriate Event item to get this to display the correct
photo for anything past the 1st.

Also should note that I have attached the photo record report as a
sub-report (which has the MS image display code) embedded in the main
report. If I display it one record at a time, the photos change, but if I
view them as a continuous forms, they are all displayed as the first
photo.

If everything's the same, then that likely means you are using an unbound
control in the continuous forms view. If so, then it is working as
designed -- there is only one detail for that form, and copies are shown
with controls filled in from particular records, but unbound controls
contain the values set in the active record. You'll have to use a different
approach to displaying the images, in this situation. You might also revise
your report design, with a query that has multiple details for each
"whatever" and put the "whatever" in a group header.

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.

And, Stephen has an ActiveX control available that works in cases where the
graphics filters are not available -- and works better, I've heard, than the
OLE Object and OLE Controls.

Please note that there are other approaches, e.g.,
Application.FollowHyperlink, but those, like OLE and Bound OLE Frames (which
from the symptoms you describe, are what you were / are using) still leave
you "at the mercy of the imaging software registered for the filetype").

Finally, Access 2007 has enhancements that, reputedly, eliminate the
database bloat long associated with OLE Objects and Bound OLE Frames. But,
it still leaves you relying on the software registered for the image type,
which may not be as "cooperative" as we'd like in creating our display. It
also has the capability of having a variable number of Attachments to a
Record, which may be helpful. But, as I have not done much with it yet, I
certainly wouldn't suggest you rush out and replace an earlier version --
until you have a copy incorporating, at least, the first Service Pack, or
have
the SP in hand and ready to apply as soon as you install Access 2007.

Larry Linson
Microsoft Office Access MVP