Paul Doree said:
How do I get an ole field on a form to display full frame.
At the moment, all I can get it to do is show a small (and
rather blocky) verion of a .bmp file, with the file name
underneath. It won't display .jpg at all - only
the file name.
I've played with this for a while now.
We couldn't even play with it to determine what version of Access you are
using, what Control you are using to attempt to display the OLE field. You
have the advantage of having the database in front of you; we are dependent
on your telling us, in detail, precisely, and concisely... with all the
informaion available, remotely debugging your code is not easy; without that
information, it is simply not possible.
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 former 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.
Larry Linson
Microsoft Office Access MVP
