Linked Images in Report in MSAccess 2003

[ChuckPederson]

Ok, Microsoft's online help for my topic seems to be
written for some other version of Access.

Here is what I have
- A table with a text field called "title" and another
called "picture". In the second field is the path to a
picture for example "image1.jpg" (According to Microsoft,
I can use relative addressing)

What I want to do ...
- Create a report that will display all the linked
pictures with their titles.

So, I create a report and using Access2003's Toolbox, I
add a "Bound Object Frame". I go into the properties and
change the 'Control Source' to "picture".

Then I preview my report and I get a blank white box.

Some other things I have tried
- Other image formats like .wmf
- using a full path
- Trying the "Add a picture or object" MS Help, but it
refers to such things as "OnCurrent" and "AfterUpdate"
which I cannot find in any properties box.

Any suggestions? Thanks,

Chuck

 

[Larry Linson]

"ChuckPederson" wrote

Here is what I have
- A table with a text field called "title" and another
called "picture". In the second field is the path to a
picture for example "image1.jpg" (According to Microsoft,
I can use relative addressing)

What I want to do ...
- Create a report that will display all the linked
pictures with their titles.

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.

In Reports, any code that would, for Forms, be in Current event can be
placed in the Print event.

Larry Linson
Microsoft Access MVP