images as OLE objects

[Guest]

on 2 computers, in ACCESS2000, when I try to insert same images (JPEG format)
from a file on c:drive into a table (OLE object field), it works OK on one
computer, but not on the other (instead of the image, the word "PACKAGE" is
inserted). Double-click on the image displays it in Microsoft Photo Editor
(the one that is OK) and in Windows Picture and Fax Viewer (the one that is
not OK - has no Microsoft Photo Editor).
Any advice on how to make it work on both computers would be greatly
appreciated.
SM


I can not find any references to "PACKAGE" in ACCESS_Help, and have not
been able to find any

 

[Larry Linson]

on 2 computers, in ACCESS2000, when I try to insert same images (JPEG
format)
from a file on c:drive into a table (OLE object field), it works OK on one
computer, but not on the other (instead of the image, the word "PACKAGE"
is
inserted). Double-click on the image displays it in Microsoft Photo Editor
(the one that is OK) and in Windows Picture and Fax Viewer (the one that
is
not OK - has no Microsoft Photo Editor).
Any advice on how to make it work on both computers would be greatly
appreciated.
SM

I've said before, and I will say again: when you use OLE Objects for images,
you put yourself at the mercy of whatever software is registered for the
image file type on the user's computer. That is obvious, in your case: one
has Microsoft Photo Editor and the other has Windows Picture and Fax Viewer.
Not only the software, but the default settings of that installed software,
can affect what you see.

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

 

[Guest]

Larry, many thanks for your response.
I had read your previous writings and those referenced, and some of the
postings in this discussion group re images in ACCESS, but did not manage to
make clear in my question what I was really after.
The images I use are never updated - they show objects that never change -
so it seemed that OLE method was suitable (also I could not get the linked
method to show the images on forms).
my query is really about the possibility of being able to set the defaults
for OLE image handling within ACCESS so that if I take my database (on a CD)
to different computers (different locations), I would be able to add new
records (objects) to the database with images provided at the time as stored
on those computers, without having to worry about what softwrae they run, or
any conversion. Is this possible? Have I been able to state my thoughts
clearly?

Many thanks again.
SM

 

[Larry Linson]

. . . without having to worry about what softwrae
they run, or any conversion. Is this possible? Have
I been able to state my thoughts clearly?

If I understand correctly, you would like to eliminate the uncertainty of
whatever software the user has registered for the file type from the
situation, and still use OLE Objects. By definition, that is not possible,
because displaying the images stored in OLE Objects is performed by whatever
software the user has registered for that file type.

It is because of this uncertainty that I avoid using OLE Objects in any
database application that will be distributed to others -- it's OK on my own
machine, because I know what graphics applications will be
available/registered.

On the other hand, unless the user has installed Office Pro, or has
standalone Microsoft Word installed, the graphics filters may not be
available to use an Image Control with some image file formats (e.g., the
very popular .JPG).

Visit MVP Stephen Lebans' site, http://www.lebans.com, and see if there's
something there that will assist you in displaying the images. I believe he
does have some controls that may apply.

Larry Linson
Microsoft Access MVP

 

[Guest]

Hi Larry,

If I understand correctly, you would like to eliminate the uncertainty of
whatever software the user has registered for the file type from the
situation, and still use OLE Objects.

Yes, that is correct.

By definition, that is not possible,
because displaying the images stored in OLE Objects is performed by whatever
software the user has registered for that file type.

I am trying to find out if it is at all possible to intervene and to
re-direct (override) user software to using methods/facilities/values I
prescibe in ACCESS databse.

It is because of this uncertainty that I avoid using OLE Objects in any
database application that will be distributed to others -- it's OK on my own
machine, because I know what graphics applications will be
available/registered.

In this application, I am the only user of the database but on different
computers at different physical locations (to obtain the latest data and
images and produce appropriate stats/information/image analyses at each
visit) - the idea is to carry the updated database on a disk/CD and to avoid
carrying a laptop around.

On the other hand, unless the user has installed Office Pro, or has
standalone Microsoft Word installed, the graphics filters may not be
available to use an Image Control with some image file formats (e.g., the
very popular .JPG).

Visit MVP Stephen Lebans' site, http://www.lebans.com, and see if there's
something there that will assist you in displaying the images. I believe he
does have some controls that may apply.

I will pursue and explore this matter as you have suggested to see what I
can find and do.

Again, many many thanks for your help.
SM

 

[Larry Linson]

My solution is to either use the "external files" or the "BLOB" approaches
from the reference. Fortunately, the users at all my clients' locations have
full Office Pro, including the graphics filters, installed, so the Image
control will work nicely. If both the computers you are using have either
full Office Pro, or standalone Microsoft Word, with graphics filters, then a
similar approach might be applicable.

Larry Linson
Microsoft Access MVP