Pictures

[Ty]

Hello.

I have a database with several fields - 2 of them are OLE for adding
pictures. This has worked fine, however, it is now 1.7 Gig. is size. This
is getting out of control.

I need another solution. I tried DBPix, however, their technical support is
lacking in helping me implement it.

I need a fairly straight forward solution that allows me to add 2 Pictures
per record without the massive size of nearly 2 Gig.

Thanks for any help / suggestions !

Ty

 

[Larry Linson]

I have a database with several
fields - 2 of them are OLE for
adding pictures. This has worked
fine, however, it is now 1.7 Gig.
is size. This is getting out of control.

I need another solution. I tried DBPix,
however, their technical support is
lacking in helping me implement it.

I need a fairly straight forward solution
that allows me to add 2 Pictures
per record without the massive size
of nearly 2 Gig.

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 (and explains the
"database bloat" that results from using OLE Objects and Bound OLE Frames to
hold and display the pictures). 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.

Larry Linson
Microsoft Access MVP