Can't display resized Images

[Richard Shaw]

I am running Microsoft Access Version 2000 (9.0.3821 SR-1)
on my Millennium system. When I set the data type of a
Field as OLE Object, this is what happens. If I insert an
image that is from a digital camera image, or an image
from something I scanned, it inserts the word "Package"
in the record in that field. Clicking on "Package" opens
the image.
However, If I had changed the size of the image in my
ACDSee editor and saved it in the same .jpeg format as the
orugunal, it will not insert the image
container "Package".
In addition, Access freezes, requiring me to exit and
reopen the application. Is this supposed to happen? Can I
never dispay images which I have resized?.

 

[Exponent]

Are you sure that the images before and after editing have exactly the same extension ? (eg maybe one is
jpg and the other .jpeg ?)
It sounds like a different OLE server is being used, and the only reason I can think of is due to a different
extension.

Having said that, using OLE Embedding this way for jpeg images can be fraught with problems - this kind
of config issue is just one of them. For example, certain common OLE Servers used for jpeg cause an overhead
of between 5 and 100 *times* the size of the original file, and can also make it impossible to extract
the original file, and difficult to set up and maintain on multiple machines.

Usually, if the images need to be stored actually in the table then raw binary storage works best. Otherwise
just store the text filename (or generate it from other fields) and load the image into an image control
from disk at runtime.

 

[Adrian Jansen]

Worse still, according to info on Stephan Lebans site, is that the case of
extensions matters !

myimage.jpg is handled differently from myimage.JPG



--
Regards,

Adrian Jansen
J & K MicroSystems
Microcomputer solutions for industrial control

Are you sure that the images before and after editing have exactly the

same extension ? (eg maybe one is

jpg and the other .jpeg ?)
It sounds like a different OLE server is being used, and the only reason I

can think of is due to a different

extension.

Having said that, using OLE Embedding this way for jpeg images can be

fraught with problems - this kind

of config issue is just one of them. For example, certain common OLE

Servers used for jpeg cause an overhead

of between 5 and 100 *times* the size of the original file, and can also make it impossible to extract
the original file, and difficult to set up and maintain on multiple machines.

Usually, if the images need to be stored actually in the table then raw

binary storage works best. Otherwise

just store the text filename (or generate it from other fields) and load

the image into an image control