Keeping Photo editor as the OLE server in Access?

[boe]

Hello,

I've created a database inventory with many pictures in it that I designed
to use photo editor from a previous version of Office since I can't find an
ole server in the current or next version of Office. I'd prefer not to
have to recode everything to make it work in one of the other cumbersome
methods discussed for inserting pictures in an access database. I've
installed just the photo editor section of Office XP and in the past that
has always worked, but I think one of the live patches for office is now
removing that feature. It will work for a few days but eventually I'll boot
and when I go to insert a picture it goes in as a package which means many
display issues for the picture in reports, forms, etc. Could someone tell
me how to prevent it from reverting back to a package?

Thanks!

 

[Larry Linson]

Hello,

I've created a database inventory with many pictures in it that I designed
to use photo editor from a previous version of Office since I can't find
an ole server in the current or next version of Office. I'd prefer not
to have to recode everything to make it work in one of the other
cumbersome methods discussed for inserting pictures in an access database.
I've installed just the photo editor section of Office XP and in the past
that has always worked, but I think one of the live patches for office is
now removing that feature. It will work for a few days but eventually
I'll boot and when I go to insert a picture it goes in as a package which
means many display issues for the picture in reports, forms, etc. Could
someone tell me how to prevent it from reverting back to a package?

Photo Editor has remained on my computer ever since I installed Office XP,
but then I did not _replace_ Office XP with Office 2003, but have them both
running side by side. I am on Windows Update, so I get all the Office SPs
and patches.

Larry Linson
Microsoft Access MVP

 

[Larry Linson]

Perhaps the following may be of help... it seems clear that you are using
OLE Objects and OLE Frames... there are other approaches, and I believe MVP
Stephen Lebans has an ActiveX to display JPG files without using OLE, just
in case your users don't have the graphics filters installed or available.

Larry Linson
Microsoft Access MVP

 

[Larry Linson]

Perhaps the following may be of help... it seems clear that you are using
OLE Objects and OLE Frames... there are other approaches, and I believe
MVP Stephen Lebans has an ActiveX to display JPG files without using OLE,
just in case your users don't have the graphics filters installed or
available.

Sorry, fingers too quick for brain -- sent the original without pasting in
the following that may be of 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

 

[Sytoby]

I am having a similar problem. I insert a BMP file into an OLE field and I
get Package instead of Bitmap Image. I am using Access 2003. This problem
is really causing me troubles.