How to paste photos

[Guest]

I have a database of applicants with their photos.
Filed name for photos is: photo.
I have chosen OLE object as data type in table design. Is this true?
I have the photos in jpg format.

How to Input (or import) the photo?
In table input mode, I right click in the photo field and choose: "Insert
object"
In Insert object window I click buttun: "Creat from File" and give the path.
It doesn't bring the photo but writes "package" in table. But it doesn't show
the photo when I browse my database in Report.
What is the best and easiest way to bring the photos to Access and vire them
in Report and print them out?

 

[Guest]

completing my question, in form view it only shows the file name of photo jpg
file in the photo filed but doesn't show the photo itself. Showing the file
name may mean that it is imported but I need one more step to show the photo
itself.

 

[Douglas J. Steele]

You really shouldn't store the pictures in the database, but just store a
link to where the picture is on the hard drive: Access is very inefficient
on storing images.

If you really want to store them in the database, though, check the sample
imaging databases at http://accdevel.tripod.com. They 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.

If you've already starting storing images in your database, and you'd like
to export them all, see:
http://www.lebans.com/oletodisk.htm

 

[Guest]

Dear Douglas
Thanks for your reply full of information regarding photo issue in Access.
This time I have only 14 photos so the memory is not a big issue for me but
for next tasks I will consider, putting only photo link in Access.
Let me read referenced links in your reply and reach you again.
--
Rasoul Khoshravan Azar
Civil Engineer
Osaka, Japan

You really shouldn't store the pictures in the database, but just store a
link to where the picture is on the hard drive: Access is very inefficient
on storing images.

If you really want to store them in the database, though, check the sample
imaging databases at http://accdevel.tripod.com. They 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.

If you've already starting storing images in your database, and you'd like
to export them all, see:
http://www.lebans.com/oletodisk.htm

 

[Guest]

Dear Douglas
I gave up the method to copy and store the photos inside db.
Could you please kindly tell me the standard procedure to include links to
photos?
I simply write click in the photo field (in table) and follow the
directions. It shows the message package in the photo field after finishing
but it doesn't show either in table, form or report. Am I doing something
wrong?
--
Rasoul Khoshravan Azar
Civil Engineer
Osaka, Japan

You really shouldn't store the pictures in the database, but just store a
link to where the picture is on the hard drive: Access is very inefficient
on storing images.

If you really want to store them in the database, though, check the sample
imaging databases at http://accdevel.tripod.com. They 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.

If you've already starting storing images in your database, and you'd like
to export them all, see:
http://www.lebans.com/oletodisk.htm

 

[Douglas J. Steele]

The sample databases to which I pointed you should show you what you need.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

Dear Douglas
I gave up the method to copy and store the photos inside db.
Could you please kindly tell me the standard procedure to include links to
photos?
I simply write click in the photo field (in table) and follow the
directions. It shows the message package in the photo field after
finishing
but it doesn't show either in table, form or report. Am I doing something
wrong?

 

[Guest]

Through the link you mentioned, I was referred to:
http://support.microsoft.com, you can find the Access Knowledge Base.
Article Q158941, “ACC: How to Load OLE Objects from a Folder into a Tableâ€
It says it is applicable to Access 95 & 97 at the end. I suppose there might
be easier way in Access 2003. Isn't there?
I will follow as the instruction in that Knowledge Base but if there is any
easier way in AC2003, let me know.
I do remeber once I made student ID cards with Access long time ago and
stored photos inside my db.
but on that time I didn't face such a difficult task of dealing wwith photos
in ACCess.

 

[Guest]

I am trying to utilize following knowledgebase article:
ACC: How to Load OLE Objects from a Folder into a Table
Article ID : 158941

What is the Class in the MAcro written in that article?
Larry Linson also points out this issue. He says: "I omitted that and it
seems to work quite well without setting the Class property"

In my case the program loaded the photos but viewing in a report, it only
shows the jpg icons not photos itself.
Could you please kindly hint one more step to finalize the task.
TIA

 

[Guest]

sorry the knowledge base says:
NOTE: To determine the Class name of an OLE object, see the documentation
for the application supplying the object.
But my objects are ordinary jpg photos I have got from my applicants through
Internet (email).

You hav ementioned about printing problem but in my case the problem is
displaying the photos.

 

[Guest]

Dear Douglas
Finally I was able to solve my problem.
Photos seams to have different sizes so when they are displayed in REport
preview (Still I have not been able to display them in Form) they are cut in
top or buttom. Is there any command to resize the photo size to fit the
allocated box precisely.

 

[Larry Linson]

Finally I was able to solve my problem.
Photos seams to have different sizes so when they are displayed in REport
preview (Still I have not been able to display them in Form) they are cut in
top or buttom. Is there any command to resize the photo size to fit the
allocated box precisely.

The SizeMode of the Image control, set to Zoom, will fill the Image Control
as best it can while still maintaining the aspect ratio (that is, not
distorting the picture). Set to Zoom, it will fill the Image Control both in
height and width, but will distort the picture, if need be, to fill the
Control.

I find it problematical, at best, to try to display the content instead of
the icon when using Unbound Object Frames. That's another reason I avoid
using OLE Objects and Object Frames for display.

Larry Linson
Microsoft Access MVP