Access 2003 image bloat?

[Yair Sageev]

Hi all,

I know that with Access 2002 and earlier versions the database bloats
enormously when you embed images as OLE types in the database. I'm
wondering if this flaw has been corrected in Access 2003.

Sadly, I'm not able to use the BLOB or linked image approach because the
images need to be displayed in a continuous subform.

Thanks in advance.

 

[Stephen Lebans]

Easy answer...NO.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.

 

[Yair Sageev]

Thanks for the easy answer!

Easy answer...NO.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.

 

[Richard Moldwin]

Hi Yair,

There is a solution to your problem. Several companies
sell image controls that store raw image data (even
preserving JPEG compression) in the Access OLE field or
the SQL Server Image field. In my hands, there is
absolutely NO BLOAT, and the byte size of the field is
EXACTLY the same size as the size of the disk file.

The control that I am currently using is THBImage
(standard edition), at www.THBComponents.com. It costs @
$150. It is a really great addition to Access, and it
works in Access 2002/XP (and I guess 2003) with just a few
lines of code. The Pro and Enterprise versions include
many features for graphics manipulations in Access, and
allow you to use advanced JPEG 2000 compression with
minimal loss of image detail - this is great for database
storage. There is also an add-on for TWAIN scanning into
your image field.

There are other controls available, but I have had some
trouble getting them to work in Access 2002, especially
when you need multiple image formats and support for image
compression. So, my suggestion is THBImage.

--Rich