Bound Photographs

  • Thread starter Thread starter ralphslot
  • Start date Start date
R

ralphslot

It seems I can only get the File Name into a Bound Frame
and not the Photograph itself (.bmp & .jpg). This is into
a Form. Can anyone help.
Thank you.
 
Don't use a bound frame; use an image control (found in toolbox) and set the
picture property to the path of your photograph.
 
ralphslot said:
It seems I can only get the File Name into a Bound Frame
and not the Photograph itself (.bmp & .jpg). This is into
a Form. Can anyone help.
Thank you.
Click to expand...

Do you have the Photo Editor or some other program that lets Access display other image formats installed? Before I installed the needed filters on my PC, Access would only show JPEG's as icons.

Matt
 
Sorry, I think I am confusing you by not telling you the
whole story.

I'm trying to make a database of my collection of old
photographs. From what I read, I understood that I was
required to put the photographs into a bound frame, as I
needed a different photograph on each record.

The problem still remains; I can't get the picture to
show only the files path.

Thank you, Ralph
 
Nope, same answer. Your table shouls look like:
TblPhotograph
PhotographID
PhotoDesc
Photopath

Put the full path including drive letter in Photopath

Base your form on TblPhotograph. You need three textboxes and an image control.
Bind all the fields to the textboxes. The image control is unbound. Put the
following code in the OnCurrent event of the form:
Me!NameOfImageControl.Picture = Me!Photopath
 
ralphslot said:
It seems I can only get the File Name into a Bound Frame
and not the Photograph itself (.bmp & .jpg). This is into
a Form.
Click to expand...

Perhaps you have been misled to think that the only way to do photographs is
via OLE Objects and Bould OLE Frames. That is not the case, as someone has
said. 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
 
Back
Top