images won't display

[merlin777]

I'm just starting out in access and I've come across a problem.

I've embedded images in my table, OLE embedded.
When i create a report i can add a bound frame but when i preview the report all i get is the generic image icon (its a jpg), the filename and the words (command line).

any idea whats happening?

 

[choytw]

I may not be able to help you since I am probably one of the least knowledgeable here, but are your pictures attachments inside the DB or links to pictures on your computer/network drive?

 

[merlin777]

i've tried both.

it just seems to me that the whole image handling thing in access is unnecessarily clunky and complicated. For instance, for anything other than a bitmap (and who uses those as a default image format?) requires another piece of software to be present and registered to access to merely display a jpg - mad!

i'm contructing a DB at home to use at wok. What if the older system at work doesn't have the other software present? I'm not going to be able to argue having that installed on every user's pc throughout the company!

at the moment i'm afraid I prefer excel....

 

[Montez659]

While I may not be able to help with your image issue, you need to look into late-bound or late-binding (I think that is what it is called). This will essentially let you create an object in Access even if Access doesn't have a library set for it. Not sure if it will work in this particular instance with the pictures, but worth a check.

 

[HiTechCoach]

Access can easily handle a .bmp format because Windows has the ability natively to handle this format. There are many other formats. That is why have to isntall software to handle the image.

OLE by definition is the linking of data and an external program to handle the data. So if you use OLE then you must also install the software to handle the data.

There are also many issues with storing OLE images. The biggest is that it causes tremendous database bloat. You will quickly reasch the 2 gig database limit is you start storing very many OLE images..

I work with some very large scale document management systems that use an SQL server. There are millions of documents and scanned images of documents stores. None are actually stored in the database.

The trick I use is to store just the path to the image. I use the Web Browser control to display the image.

I have created an example iof how to store teh path. See: Document Links 2


What version of Access are you using?

 

[HiTechCoach]

While I may not be able to help with your image issue, you need to look into late-bound or late-binding (I think that is what it is called). This will essentially let you create an object in Access even if Access doesn't have a library set for it. Not sure if it will work in this particular instance with the pictures, but worth a check.

Early or Late binding have to do with VBA code. It has has nothing to do with OLE.

Object embedding means you can insert information created by another application into your Access tables.

That is why OLE requires the software to be installed.

The may help: Using OLE

 

[Montez659]

HiTech - thanks for the clarification!

 

[choytw]

I guess I am confused now. I was able to handle JPEG and GIF files in the DB I was working on without downloading any external software/plugin. Does 2007 come with this functionality or are you only referring to pictures stored in the DB and not those which are linked?

 

[HiTechCoach]

I guess I am confused now. I was able to handle JPEG and GIF files in the DB I was working on without downloading any external software/plugin. Does 2007 come with this functionality or are you only referring to pictures stored in the DB and not those which are linked?

Embedded OLE objects are the biggest problem. OLE in generally is problematic when working with images. It has been this with for 15+ years.

It is true that Access 2007 does handle jpg and gif files better than prior versions. IIRC this is due to the new Office Picture Manager that replaced the Photo Editor in prior versions.

It is considered by most Access Experts/Gurus that the Best Practice is to not use OLE.

When I do store some images in my database I do it as a BLOB. I then extract the file to the hard drive before using it as an external file.

I have seen previous post over the last 7+ years on the subject. IIRC most peopel stopped using OLE to store images. I will do some checking to see if there is an actual fix to your issue.

 

[HiTechCoach]

I still have not found a solution.

I also was not able to duplicate the issue.