"Ntl News Group" wrote
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.
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?
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
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.zi p 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