Handling Picture in Access Database

[Ulrike]

I need to bind in (thumbnail-sized) pictures into an Access Database
in such a way that there is one picture for each record (abt. 3000
records on the whole). Ideally, the pictures should show on the Form.
Until now, I have embedded OLE-objects and have inserted each picture
manually in the records - but the pictures do not show in the Forms. I
have to double-click an icon and then, the picture will open in an
external programme.
PROBLEM WITH THIS: I want to publish my database (result of a
research-project) in form of a CD-Rom. - When the CD-Rom version is
used, and the picture is opened, the entire Database-programme gets
stuck, because the picture does not close properly; it is waiting to
be "Saved" which is not possible on a CD Rom.

NEED URGENT HELP!

[Konstantinos]

Hello Ulrike,

you might want to take a look here
http://www.mvps.org/access/forms/frm0030.htm

Cheers
Konstantinos

"Ulrike" <sa***@nus.edu. sg> wrote in message
news:f9******** *************** ***@posting.goo gle.com...

I need to bind in (thumbnail-sized) pictures into an Access Database
in such a way that there is one picture for each record (abt. 3000
records on the whole). Ideally, the pictures should show on the Form.
Until now, I have embedded OLE-objects and have inserted each picture
manually in the records - but the pictures do not show in the Forms. I
have to double-click an icon and then, the picture will open in an
external programme.
PROBLEM WITH THIS: I want to publish my database (result of a
research-project) in form of a CD-Rom. - When the CD-Rom version is
used, and the picture is opened, the entire Database-programme gets
stuck, because the picture does not close properly; it is waiting to
be "Saved" which is not possible on a CD Rom.

NEED URGENT HELP!

[Larry Linson]

"Ulrike" wrote

I need to bind in pictures into
an Access Database in such a
way that there is one picture for
each record (abt. 3000 records
on the whole). Ideally, the pictures
should show on the 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.zi p 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.

Larry Linson
Microsoft Access MVP