Why my DB Access is too Big ?

  • Thread starter Thread starter Claudio Ferroni
  • Start date Start date
C

Claudio Ferroni

I've build a DB using a lot of picture.

BUT .... I'm using the link feature of the picture ... I did not
include the picture in the DB ..... BUT probabilly I've mistake in
something.

Could you somebody provide me how to verify if I have used correctly
the LINK feature instead of inlcuding directly the picture ?

Maybe my question is not be very clear .... it is only english problem
=:-)


Best regards to all.

Ciao

Claudio
 
I've build a DB using a lot of picture.
Click to expand...

That's the problem.
BUT .... I'm using the link feature of the picture ... I did not
include the picture in the DB ..... BUT probabilly I've mistake in
something.
Click to expand...

No. You didn't make a mistake; Microsoft did!
Could you somebody provide me how to verify if I have used correctly
the LINK feature instead of inlcuding directly the picture ?
Click to expand...

Whether you link to the picture *or* import the picture, Microsoft
designed Access in such a way that it wastes a HUGE amount of disk.

To get around the problem, most developers don't store image data in
Access tables *at all*. Instead, you can store the image in a graphics
file in a folder on your disk, and store the file and path name to the
image file in a Text field in your table. See

http://www.mvps.org/access/forms/frm0030.htm

and the references there for sample code.
 
"Claudio Ferroni" wrote
I've build a DB using a lot of picture.

BUT .... I'm using the link feature of the
picture ... I did not include the picture in
the DB ..... BUT probabilly I've mistake
in something.
Click to expand...

No, it is a characteristic of pictures stored in or linked to OLE Objects.
John's discussion and suggested solution is one way, but it's not the only
one. There's detailed information in the article accompanying the sample
databases that you can freely download from http://accdevel.tripod.com --
they illustrate three approaches to handling images in Access, two of which
do not suffer from the bloat you describe.
 
John Vinson said:
No. You didn't make a mistake; Microsoft did!


Whether you link to the picture *or* import the picture, Microsoft
designed Access in such a way that it wastes a HUGE amount of disk.
Click to expand...

Just to be contrary I'm not so sure this was a mistake on MS's part.
Now it's not as useful in this day of fast processors.

What is really happening, AFAIK, is that the file and/or link is being
copied inside the Access MDB as a .bmp file. .bmp files are horribly
inefficient be definition. However they don't take any processing
power to decompress an image. Try viewing an jpg vs. bmp image on a
386. I think you'll find a huge difference in performance.

And back then in A1.0 days back in '93 the Pentium was just introduced
so MS had to develop to a 486 environment.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Back
Top