How do I display images from a folder in a form : access 2003

[gnome88]

I have tried to implement m/s solution q285820 to display images from a
folder in a form. I have 30 different pictures which I would like to
associate with 30 entries in a table and display in a form.

When creating the 'form' per the solution method discribed in q285820, I am
not sure how to proceed in creating the 'image control'. In access 2003, I
have the choice of 3 image control options from the toolbox. When using the
plain 'image control', I have to associate a specific file for 1 image. I
have not been able to figure out how to properly construct the form.

Can someone give me a solution?

Thanks -- gnome88

 

[Arvin Meyer [MVP]]

This is the method I use to store image paths and display them:

http://www.datastrat.com/Download/Picture2K.zip

 

[Larry Linson]

I have tried to implement m/s solution q285820 to display images from a
folder in a form. I have 30 different pictures which I would like to
associate with 30 entries in a table and display in a form.

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

Larry Linson
Microsoft Office Access MVP