ftaghaboni said:
I have used your A2KAutosizeOLEVer6 to create a database that generates
reports with pictures and the pictures are autosized. I was wondering if
it
is possible to integrate this function with the functions in your
A2KLoadSaveJpegVer9 so I could reduce the size of my database since I will
have hundreds of pictures in there.
If you save your JPEG as an OLE Object, Access and the program registered
for JPEG will cooperate to create a thumbnail that is stored along with the
JPEG, but the thumbnail will be in uncompressed bitmap format. Thus a small
JPEG will take an enormous amount of space when stored as an OLE Object.
What you propose will not significantly reduce the size if you continue to
store the pictures as OLE Objects.
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.
Larry Linson
Microsoft Access MVP
