Pictures in Access 97 and 2000

I have a 97 database and want to embed (not link) a picture on a form
and report

The picture is just a scan of a signature, I am storing it in a table as
an OLE object, then on a form I copy and paste this 17KB JPG into the
database.

The problem is that Access then shows it as a Icon and not as a picture.

I have set the forms properties:
Size Mode = Zoom
Display Type = Content
Update Options = Auto
OLE Type = Either

Regards

re: Pictures in Access 97 and 2000

Ntl News Group wrote:Do you need to store lots of them or just one? You can embed an image without
storing it in an OLE field. Just paste it into design view.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

re: Pictures in Access 97 and 2000

Ntl News Group wrote:I need to store everal of them not just one and need the user to be able
to change them without going into design view.

re: Pictures in Access 97 and 2000

"Ntl News Group" wrote
I don't understand what you mean by "then on a form I copy and paste this
17KB JPG into the database" -- if the picture is stored as an OLE object, it
is already "in the database." If you'd be a little more specific about what
you are doing with it, someone might be better able to help. Do you have a
Bound OLE frame on the Form into which you are trying to paste the image? If
you are using a Bound Object Frame, have you bound it to the image? Are you
trying to paste the image into the Picture property of the Form itself?
If you are using a Bound Object Frame, is the Display Type property of the
Frame set to "Content"? If it is set to "Icon," you can expect to see an
icon.

On the other hand, whenever you use an OLE Object and Bound Object Frame,
you "put yourself at the mercy" of whatever COM-compliant software is
registered by the user to handle that type of image.

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

re: Pictures in Access 97 and 2000

Dear Larry,
I have a similar problem and have read eveything I could find...I have
a 2002 database with an OLE object which is a field in a table of the
database, then I have a bound frame on a report...on my computer the
picture shows up just like I want, but on another computer I just get
an icon....I had given up finding an answer until I saw your message
this morning and you are mention COM...if you have the time and
patience to point me in the right direction I would really appreciate
it.
Thanks,
Debbie

re: Pictures in Access 97 and 2000

COM (Component Object Model) is an inter-program communication protocol used
to allow separate applications to work together. In the "file types" tab of
Folder Options, you'll find programs registered to handle different file
types... there will be one, most likely, for .jpg. The capabilities and
settings of that program will affect what you see when you use OLE (Object
Linking and Embedding) Objects for your images. And, it is difficult, if not
impossible, to predict what the interaction between that registered imaging
software and Access OLE Objects / Bound Object Frames is going to be.

Working with images in OLE Objects and Bound Object Frames is such an "iffy"
thing that many of us (myself included), avoid that approach when we can.
And that is one reason I prepared the examples you can obtain from the link
I provided.

Larry Linson
Microsoft Access MVP



"debbie" <debbie@seaportnet.comwrote in message
news:1158587878.367306.20090@e3g2000cwe.googlegrou ps.com...