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.
Larry Linson
Microsoft Access MVP
"DD" <da**********@bigpond.com.au> wrote in message
news:14**************************@posting.google.c om...
I have a tblCategory which has a fldPhoto.
I will have 1 picture for each category with numerous categories.
Instead of imbedding the pic in a OLEbox i have created a picBox which
is populated with the imgPath after you browse for the file
(Me![Photo] = GetOpenFile)
This is fine however, when i place a different imgpath into each
category, the picBox for each category only shows the first img.
This runs from a report so there is only one pic box,,i thought it
would act the same as an OLE where each new category pic populates the
PicBox.
I hope i have explained this for anyone to understand.
Any help
DD
