Photo Types

[Mike Busch]

I used a OLE object to insert photos in to records for an
Access form. One photo per record. When I use the form
the bitmap photos are thumb nail size and the jpg's are
just an Icon of a jpg with the name of the Jpg. What do
I need to do to see these photo's as normal size. Thanks
in advance.

 

[Andy]

Mike;

Found this at Access support center:
258644 ACC97: A Linked JPEG File Is Displayed as an Icon on a Form.
W/this resolution:
Open the Employees table in Datasheet view.
Right-click the OLE Object field, and then click Insert Object.
In the Insert Object box, click Create New.
Under Object Type, click Microsoft Photo Editor 3.0 Photo, and then click
OK. Microsoft Photo Editor opens.
In Photo Editor, in the New dialog box, click Open an Existing Picture, and
then browse to the JPEG file that you want to insert.
Click the JPEG file. The picture opens in Photo Editor.
On the File menu, click Exit and Return to tablename : Table.

Although it states that it is for ACC97 it also works for ACC2K. It isn't
the final answer because I had to re-insert all of the photos, but it's a
start.

The above is a partial answer. After a few more months of searching,
discovered that MSPhotoEditor needed to be re-installed from the Office CD.

Andy

 

[Larry Linson]

I used a OLE object to insert photos
in to records for an Access form. One
photo per record. When I use the form
the bitmap photos are thumb nail size
and the jpg's are just an Icon of a jpg
with the name of the Jpg. What do
I need to do to see these photo's as
normal size.

There's a property somewhere to "display thumbnail", but I don't use OLE
Object photos very often because of the bloat. The following may be of some
help:

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