Be very careful using this approach to store images in tables. In some situations it can cause a storage
overhead of up 10 to 100 *times* the size of the original file, and associated system and network load.
This may be less apparent with an SQL Server back-end in place of Access.
It is also highly dependent on the correct configuration of client systems, regarding installed OLE Server
applications and file associations. This can be difficult to maintain over several systems or different
OS and application versions.
To avoid these and other possible problems when storing images (embedded) in tables, you can store the
images as raw binary data. This also avoids potential data loss issues when extracting (loss of quality/compression/metadata),
and interoperabilit y issues (IIS, VB etc).
I don't know of a standard way to resize images using Access. Ideally you should consider using a resampling/interpolation
algorithm to generate images at different resolutions like this (eg thumbnails). This usually gives much
better results than a standard resize operation.
Finally, if you would consider using a commercial control, may I suggest that you take a look at our 'DBPix'
image control for Access, which should be able to do exactly what you require with little effort. See
the link below for more info.
--
_______________ _______________ _______________ __________
http://www.ammara.com/
Image Handling Components, Samples, Solutions and Info
DBPix 2.0 - lossless jpeg rotation, EXIF, asynchronous
dh******@parkpl ace.co.uk (Dom Hicklin) wrote:
I have created a form onto which images can be dropped and thus added
to the OLE field of a Table (Access 2000 linked to SQL 2000 server).
I use the Stephen Lebans ExportOLE function to do this and it creates
images on my shared drive beautifully!
Being new at this I wondered if there is an easy way of taking the
image whatever it's size when pasted and always exporting it as 66*75?
