OLE Object (images) in tables

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Good morning,
I have a small membership database with one table of about 200 records, from which I will be running queries and a few forms. One of the fields is an OLE object (Image) taken with a Sony Mavica digital camera. The images are saved in an image directory and seem to be associated with MS Photo Editor. What started out (after Compress and Repair Database) as 188kb is now 13.8Mb with only 2 images linked to their respective records. Linking and Embedding offer the same 13.8Mb filesize and compressing it doesn't improve things.

The table size may end up in the 250-300 range, and calculating filespace, I'm going to have to consider a hard drive upgrade if I can't get the filesize down to something more managable. What am I doing wrong?

Thanks!
Derek
 
Access/Jet is not very efficient when it comes to storing images. The best
alternative is often to store the path to the image instead of the image
itself. Here are links to several different sites that offer different
solutions for working with images in Access:

Tony Toew's Reference page - with several additional links:
http://www.granite.ab.ca/access/imagehandling.htm

Arvin Meyer's Solution:
http://www.datastrat.com/Download/Picture2K.zip

Larry Linson's Imaging Example
http://accdevel.tripod.com/
 
I really liked Arvin's solution. However, I'm not sure about the coding to make it happen. I'll also check the Access MVP site and Larry Linson's to see if there's anything there I might learn

Thanks
Dere

----- Sandra Daigle wrote: ----


Access/Jet is not very efficient when it comes to storing images. The bes
alternative is often to store the path to the image instead of the imag
itself. Here are links to several different sites that offer differen
solutions for working with images in Access

Tony Toew's Reference page - with several additional links
http://www.granite.ab.ca/access/imagehandling.ht

Arvin Meyer's Solution
http://www.datastrat.com/Download/Picture2K.zi

Larry Linson's Imaging Exampl
http://accdevel.tripod.com


--
Sandra Daigl
[Microsoft Access MVP
For the benefit of others please post all replies to this newsgroup


Derek Wittman wrote
 
I'm guessing that the easiest thing is to move toward putting an icon on each record and linking to the image. Of course, now I'm being told that we'll probably move to Church Data Master, which, from what I can tell, isn't NEARLY as powerful a tool for the nursery. To me, the more I can customize and make EXACTLY what I want, the more POWERFUL it would be.

Thanks, Sandra!
Derek

----- Sandra Daigle wrote: -----


Access/Jet is not very efficient when it comes to storing images. The best
alternative is often to store the path to the image instead of the image
itself. Here are links to several different sites that offer different
solutions for working with images in Access:

Tony Toew's Reference page - with several additional links:
http://www.granite.ab.ca/access/imagehandling.htm

Arvin Meyer's Solution:
http://www.datastrat.com/Download/Picture2K.zip

Larry Linson's Imaging Example
http://accdevel.tripod.com/
 
Ah . . . a Church application. I think we've all written one at one time or
another. My first is still in use in two Churches. While it is nice to have
control over the application there have been times when it has been a bit of
an albatross merely because I no longer have the time to devote to it. Good
luck with yours!

--
Sandra Daigle
[Microsoft Access MVP]
For the benefit of others please post all replies to this newsgroup.


Derek said:
I'm guessing that the easiest thing is to move toward putting an icon
on each record and linking to the image. Of course, now I'm being
told that we'll probably move to Church Data Master, which, from what
I can tell, isn't NEARLY as powerful a tool for the nursery. To me,
the more I can customize and make EXACTLY what I want, the more
POWERFUL it would be.

Thanks, Sandra!
Derek

----- Sandra Daigle wrote: -----


Access/Jet is not very efficient when it comes to storing
images. The best alternative is often to store the path to the
image instead of the image itself. Here are links to several
different sites that offer different solutions for working with
images in Access:

Tony Toew's Reference page - with several additional links:
http://www.granite.ab.ca/access/imagehandling.htm

Arvin Meyer's Solution:
http://www.datastrat.com/Download/Picture2K.zip

Larry Linson's Imaging Example
http://accdevel.tripod.com/


--
Sandra Daigle
[Microsoft Access MVP]
For the benefit of others please post all replies to this
newsgroup.


Derek said:
Good morning,
I have a small membership database with one table of about 200
records, from which I will be running queries and a few forms.
One > of the fields is an OLE object (Image) taken with a Sony
Mavica > digital camera. The images are saved in an image
directory and seem > to be associated with MS Photo Editor.
What started out (after > Compress and Repair Database) as 188kb
is now 13.8Mb with only 2 > images linked to their respective
records. Linking and Embedding > offer the same 13.8Mb filesize
and compressing it doesn't improve > things.calculating > filespace, I'm going to have to consider a hard
drive upgrade if I > can't get the filesize down to something
more managable. What am I > doing wrong?
 
Thanks, Sandra. I appreciate the encouragement (I think that's what that was... hehe). The Nursery Director isn't sure what she wants. My wife (her assistant) has been relegated to greeter and registration - actually what she was supposed to do after all, but has MUCH more to offer.

The crux is this: I can make everything into a switchboard application with one-click-shopping, or I can make it so it takes a little bit of brains to manage it. My wife would be fantastic at running the database, importing images (icons), and administrating the weekly activities. (i.e. register at 8:45 and have the ID tag, claim checks, etc, by 10:30, after the first sermon). However, I know that Access is MUCH more powerful and can be coded/formed to play to the lowest common denominator. I could literally make systems management a full-time job for the church and fit right into it. I'd even do it and the Jr. High pastor position, but they want someone seminary-trained..

Sorry, just having that kind of day. Then again, they may REALLY want to use this Church Data Master package..

Dere

----- Sandra Daigle wrote: ----

Ah . . . a Church application. I think we've all written one at one time o
another. My first is still in use in two Churches. While it is nice to hav
control over the application there have been times when it has been a bit o
an albatross merely because I no longer have the time to devote to it. Goo
luck with yours

--
Sandra Daigl
[Microsoft Access MVP
For the benefit of others please post all replies to this newsgroup


Derek Wittman wrote
I'm guessing that the easiest thing is to move toward putting an ico
on each record and linking to the image. Of course, now I'm bein
told that we'll probably move to Church Data Master, which, from wha
I can tell, isn't NEARLY as powerful a tool for the nursery. To me
the more I can customize and make EXACTLY what I want, the mor
POWERFUL it would be
Thanks, Sandra Dere
----- Sandra Daigle wrote: ----
images. The best alternative is often to store the path to th
image instead of the image itself. Here are links to severa
different sites that offer different solutions for working wit
images in Access
Tony Toew's Reference page - with several additional links http://www.granite.ab.ca/access/imagehandling.ht
Arvin Meyer's Solution http://www.datastrat.com/Download/Picture2K.zi
Larry Linson's Imaging Exampl http://accdevel.tripod.com
Sandra Daigl
[Microsoft Access MVP
For the benefit of others please post all replies to thi
newsgroup
Good morning
I have a small membership database with one table of about 20
records, from which I will be running queries and a few forms
One > of the fields is an OLE object (Image) taken with a Son
Mavica > digital camera. The images are saved in an imag
directory and seem > to be associated with MS Photo Editor
What started out (after > Compress and Repair Database) as 188k
is now 13.8Mb with only 2 > images linked to their respectiv
records. Linking and Embedding > offer the same 13.8Mb filesiz
and compressing it doesn't improve > thingscalculating > filespace, I'm going to have to consider a har
drive upgrade if I > can't get the filesize down to somethin
more managable. What am I > doing wrong
 
I tried something new last night. I decreased each image dimension to 25% x 25%. This caused the increase in db size to go from 6Mb each image to 304k each image. And for the size of the image control on my form, this works out all right

I wouldn't even mind linking to the images as icons, but then they open up Photo Editor - and it's important to me to keep the image to the Form Window

Thanks again
Dere

----- Sandra Daigle wrote: ----

Ah . . . a Church application. I think we've all written one at one time o
another. My first is still in use in two Churches. While it is nice to hav
control over the application there have been times when it has been a bit o
an albatross merely because I no longer have the time to devote to it. Goo
luck with yours

--
Sandra Daigl
[Microsoft Access MVP
For the benefit of others please post all replies to this newsgroup


Derek Wittman wrote
I'm guessing that the easiest thing is to move toward putting an ico
on each record and linking to the image. Of course, now I'm bein
told that we'll probably move to Church Data Master, which, from wha
I can tell, isn't NEARLY as powerful a tool for the nursery. To me
the more I can customize and make EXACTLY what I want, the mor
POWERFUL it would be
Thanks, Sandra Dere
----- Sandra Daigle wrote: ----
images. The best alternative is often to store the path to th
image instead of the image itself. Here are links to severa
different sites that offer different solutions for working wit
images in Access
Tony Toew's Reference page - with several additional links http://www.granite.ab.ca/access/imagehandling.ht
Arvin Meyer's Solution http://www.datastrat.com/Download/Picture2K.zi
Larry Linson's Imaging Exampl http://accdevel.tripod.com
Sandra Daigl
[Microsoft Access MVP
For the benefit of others please post all replies to thi
newsgroup
Good morning
I have a small membership database with one table of about 20
records, from which I will be running queries and a few forms
One > of the fields is an OLE object (Image) taken with a Son
Mavica > digital camera. The images are saved in an imag
directory and seem > to be associated with MS Photo Editor
What started out (after > Compress and Repair Database) as 188k
is now 13.8Mb with only 2 > images linked to their respectiv
records. Linking and Embedding > offer the same 13.8Mb filesiz
and compressing it doesn't improve > thingscalculating > filespace, I'm going to have to consider a har
drive upgrade if I > can't get the filesize down to somethin
more managable. What am I > doing wrong
 
Back
Top