By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,689 Members | 1,718 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,689 IT Pros & Developers. It's quick & easy.

Exporting pasted Images

P: n/a
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?
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Why do you need the Images to exist on your Hard drive at that specific
size. Can you not simply resize the Image control at runtime displaying
these images to match the desired dimensions?

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
"Dom Hicklin" <dh******@parkplace.co.uk> wrote in message
news:f5**************************@posting.google.c om...
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?


Nov 12 '05 #2

P: n/a


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 interoperability 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******@parkplace.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?


Nov 12 '05 #3

P: n/a
"Exponent" <ex******@hotmail.com> wrote in message news:<3fab50dc$1@lala>...
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 interoperability 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******@parkplace.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?


I can see the overhead would be an issue in larger databases, The fact
is that the pitures are being exported to a website. These websites
are for companes with 10 to 20 employees so I'm happy to risk the
overhead.

The pictures seem to resize on the form ok but have lines on them when
they are exported to disk.

I realise the answer may be obvious but I haven't stumbled on it yet!
Nov 12 '05 #4

P: n/a


This sample may give you some ideas:
http://www.ammara.com/support/samples/showsam475d.html

When an image is first loaded thumbnail and main images are created and stored in the database (using high
quality resampling). A simple asp front-end displays the images from the live database. You can easily
spider/crawl this site to static html and image files for upload etc. Alternatively you could adapt the
sample to save the images to files at the desired resolutions when the image is loaded.
--
__________________________________________________ _____
http://www.ammara.com/
Image Handling Components, Samples, Solutions and Info
DBPix 2.0 - lossless jpeg rotation, EXIF, asynchronous
dh******@parkplace.co.uk (Dom Hicklin) wrote:
"Exponent" <ex******@hotmail.com> wrote in message news:<3fab50dc$1@lala>...
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 interoperability 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******@parkplace.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?


I can see the overhead would be an issue in larger databases, The fact
is that the pitures are being exported to a website. These websites
are for companes with 10 to 20 employees so I'm happy to risk the
overhead.

The pictures seem to resize on the form ok but have lines on them when
they are exported to disk.

I realise the answer may be obvious but I haven't stumbled on it yet!


Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.