Inserting photo or image

[JB]

Hi.
I've created a database for sketches and drawings which have been scanned.
In the form there is the name of the sketch, code, year etc but also I've
got a field that I want to insert the scanned image.
From what I can gather I right click in the field, choose 'insert object',
browse to find the image.

2 problems with that. One that the person who is going to use this database
and enter hundreds of sketch archives, is going to need something a lot
easier. Is this going to need coding to have buttons available ie. insert
picture.

And the other problem is that when I did choose an image, (bmp) it,
uncompressed, only the name of the file appears ie. 6524.bmp, if I compress
it the picture it appears very pixely, and has the name of the file
included. I only want to show the image.

I looked at the 'employee' form in the Northwind sample database and the
pictures there to insert are the same size as my images.
Can someone please point me in the right direction.
Thank you
Jen

 

[JB]

OK the second problem with the pixely is sorted. Did some tweaking.
Just need an easier way for the user to insert the sketch
Ta

 

[Larry Linson]

OK the second problem with the pixely is
sorted. Did some tweaking. Just need an
easier way for the user to insert the sketch

You may very well, sooner rather than later, need a different way to store
the images because it's easy to exceed Access' storage limits -- images are
very large.
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.

And, Stephen has an ActiveX control available that works in cases where the
graphics filters are not available -- and works better, I've heard, than the
OLE Object and OLE Controls.

Please note that there are other approaches, e.g.,
Application.FollowHyperlink, but those, like OLE and Bound OLE Frames still
leave
you "at the mercy of the imaging software registered for the filetype".

Finally, Access 2007 has enhancements that, reputedly, eliminate the
database bloat long associated with OLE Objects and Bound OLE Frames. But,
it still leaves you relying on the software registered for the image type,
which may not be as "cooperative" as we'd like in creating our display. It
also has the capability of having a variable number of Attachments to a
Record, which may be helpful. But, as I have not done much with it yet, I
certainly wouldn't suggest you rush out and replace an earlier version --
until you have a copy incorporating, at least, the first Service Pack, or
have
the SP in hand and ready to apply as soon as you install Access 2007.

Just FYI, I'd view with some alarm answers posted by a user who's said
elsewhere that he/she never ever uses bound forms.

Larry Linson
Microsoft Office Access MVP

 

[JB]

Thank you DS and Larry
Definitely have the images stored in a folder out of the database.
Lots of very good stuff. going to take some time and give it a go.
So good to have you guys out there.
Jen