Suddenly no more images - ole object

B

Basr

During a long time I use a database. I add records with data and in every
record an image. therefore I use the Ole object and I make a connection with
the images. Till now there was never a problem. Suddenly, without any reason
it is not possible anymore to add images to my records. The name of the file
becomes visible but not the image. I leaned from the microsoft site that I
can put the ole-objects into the record by using data sheet view. That's not
want I want. I want to restore the old situation. Adding the images by the
form. Another alternative from microsoft is to store the images outside the
database. That is not a solutuion for me. My database is large and it's not
acceptable to have half of the records inside the db and the other half
outside it. The problem seems to occur in more versions of Access. I think
the functionality shout not suddenly change.

Can someone help me a little to find a solution for this problem.
Access 2000, Windows XP latest updates.
thanks in advance

marcel
 
L

Larry Linson

How big IS your database? 2GB is the limit with recent versions of Access.
Have you compacted and repaired it? Do you do so regularly? What type of
image file are these images?

When you save your pictures as OLE Objects, as I am certain you are aware,
you encounter "database bloat" -- adding a 25KB .JPG file may increase
database size by 1MB or more. The reason for the database bloat is explained
in the article that is downloadable with the imaging sample DBs at
http://accdevel.tripod.com.

But, you also subject yourself to whatever the limitations, or
peculiarities, are of whatever imaging software the user has registered on
his/her computer for that type of image file.

If you are approaching the limit of database size, I know of three
solutions: (1) use a different method of storing your pictures, (2) go from
using a (the default) Jet database to using a server DB which does not have
a similar size restriction, or (3) upgrade to Access 2007 and use the new
ACCDB, in which Microsoft solved the problem of bloat.

And, while they eliminated the bloat, that did not eliminate your relying on
the imaging software the user has chosen.
Suddenly, without any reason

I am quite certain there IS some reason, though I am not certain what it is.
It could be that different imaging software has been registered for the
image file type, and that it behaves differently, or one of a number of
other causes. I've given some suggestions for trying to "track it down" near
the beginning of this response.

Larry Linson
Microsoft Access MVP
 
B

Basr

Larry Linson said:
How big IS your database? 2GB is the limit with recent versions of Access.
Have you compacted and repaired it? Do you do so regularly? What type of
image file are these images?

When you save your pictures as OLE Objects, as I am certain you are aware,
you encounter "database bloat" -- adding a 25KB .JPG file may increase
database size by 1MB or more. The reason for the database bloat is explained
in the article that is downloadable with the imaging sample DBs at
http://accdevel.tripod.com.

But, you also subject yourself to whatever the limitations, or
peculiarities, are of whatever imaging software the user has registered on
his/her computer for that type of image file.

If you are approaching the limit of database size, I know of three
solutions: (1) use a different method of storing your pictures, (2) go from
using a (the default) Jet database to using a server DB which does not have
a similar size restriction, or (3) upgrade to Access 2007 and use the new
ACCDB, in which Microsoft solved the problem of bloat.

And, while they eliminated the bloat, that did not eliminate your relying on
the imaging software the user has chosen.


I am quite certain there IS some reason, though I am not certain what it is.
It could be that different imaging software has been registered for the
image file type, and that it behaves differently, or one of a number of
other causes. I've given some suggestions for trying to "track it down" near
the beginning of this response.

Larry Linson
Microsoft Access MVP
------------


Thanks for answering.

The db is 750MB, the images are jpg's. Before the problem occured I
installed an update of Norton (NIS) and another program. These programs did
not change the registering for jpg files. When I open a jpg file Microsoft
Photo Editor is used.

When I update to Access 2007, that does not causes bloat, will my db become
smaller when I open it in Access 2007?

Marcel
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top