I have a table that I would like images to be stored to. I would like
the users to be able to add images and information about the images to
this table through the use of a form. I want them to simply be able to
click a button, find the image on their computer, and have that stored
into the table.

I know if it is not linked the database will bloat, so how would I do
this via linking? If you could point in the right direction with code,
or like an example or something that would be great. I have looked at
a few other topics about this and can't figure it out.

Gordon

<gordonmcconnell@ecragroup.comwrote

I have a table that I would like images to be
stored to. I would like the users to be able
to add images and information about the images
to this table through the use of a form. I want
them to simply be able to click a button, find
the image on their computer, and have that stored
into the table.
>
I know if it is not linked the database will bloat,
so how would I do this via linking?

The database will bloat, if you store your images as OLE Objects, even if
you Link the images. The bloating is not from your images, but from "bitmap
thumbnails" that the registered image-processing software generates at
Access' command.

If you could point in the right direction with
code, or like an example or something that
would be great. I have looked at a few other
topics about this and can't figure it out.

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

Great, I will look at your approach after lunch today. Thank you so
much for the quick response.

Gordon

Larry Linson wrote:

<gordonmcconnell@ecragroup.comwrote
>

>
The database will bloat, if you store your images as OLE Objects, even if
you Link the images. The bloating is not from your images, but from "bitmap
thumbnails" that the registered image-processing software generates at
Access' command.
>

>
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