Images

[Trond Hoiberg]

I have a database created in Access (office xp). One query is returning a
list over products. Every product has an itemnumber, lets say one has
itemnumber 1234. I then set up the query to return itemnumer, description
and 1234.jpg. The last column is computed and does not exist.
Then i tried to create a report showing every produkt AND the picture. But
that turned out to be a complicated task. It is easy to do in ASP but not in
Access.
I have tried to solve it without having to force the users to add the image
to the database as a linked object, but i am starting to suspect that they
have to do it in order for it to work. Is there a way i can avoid this?
The image will always have the same name as the itemnumber. It will always
be a jpg file and it will always be found in a subfolder under the database.
The report is an access report

I have tried to solve it using image box, unbound object frame and bound
object fra with no success

Sorry for the repost. I have posted this question in access.dataaccess.pages
forum, but i suspect it was the wrong forum
Best regards
Trond

 

[Larry Linson]

I then set up the query to return item-
numer, description and 1234.jpg. The
last column is computed and does not exist.
Then i tried to create a report showing every
produkt AND the picture. But that turned out
to be a complicated task.

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

It is easy to do in ASP but not in Access.

There are those who would disagree that it is "not easy" in Access -- I am
one who would. Perhaps after reading the article and examining the samples,
you will think it somewhat easier than you now do. From what I know about
..asp, I do suspect it _would_ be rather easy to generate the tag, once you
know the path, filename, and extension. But, of course, .asp spits out HTML
for a browser, and that isn't the way Access works. (Then again, setting the
picture property of an Image control doesn't seem very difficult to me.)

Larry Linson
Microsoft Access MVP