Database of Photographs; OLE-object?

[Mick B]

Hi

I'd like to insert photographs into my productdatabase and i used OLE-object
as a datatype for the field i want to store Jpeg files. This doesn't work.
What is wrong with te picture?

Tx

Mick

 

[Douglas J. Steele]

You probably don't actually want to store your photos in the database.
Access is very inefficient at storing images. See
http://www.mvps.org/access/forms/frm0030.htm and
http://www.mvps.org/access/forms/frm0044.htm at "The Access Web" for some
details.

If you're determined to do it, take a look at what Stephen Lebans has at
http://www.lebans.com/loadsavejpeg.htm It will avoid most of the bloat
problem.

 

[Exponent]

Access is very inefficient at storing images ***if you use OLE Embedding***.

It is perfectly capable of storing images or other binary data with little or no overhead compared to the
filesystem.

details here:
http://www.ammara.com/articles/imagesaccess.html

 

[Douglas J. Steele]

And how is your product any different than the free solution Stephen
provides?

 

[Exponent]

I wasn't advocating any one product or solution over any other, rather, trying to give more accurate information
(with real data) than statements such as 'Access is very inefficient at storing images' (which, incidentally,
are almost the exact words quoted in the article I referenced). We also frequently recommend Stephens
Solutions, and link to his site.

Since you ask, however, our product features include:

Data-binding, for minimum coding (from zero lines).
Asynchronous (background) decoding.
Lossless jpeg rotation.
TWAIN scanner and camera integration.
EXIF info viewer and enhanced metadata handling.
Zoom & pan control/config.
Automatic resampling, (for making smooth thumbnails, normalizing dimensions, reducing resolution etc.)
Great Support.