Frankie,

Why should there be any difference this practise is based on the speed that
you can retrieve blobs from a database. Maybe will this best practise change
in future.

In WindowForms the images are probably even larger because of the fact that
the used datalines are mostly faster. The DataBaseServer speed stays however
the same.

Although a little thumbnail to identify the picture in the database can help
a lot finding them and therefore  speed up the handling.

Cor

Hi Frankie,

I cannot comment on what is the best practice, but as part of my
business I have a up and running application that does exactly what you
want.

I do not store the images in the DB, but instead store them on the file
system as you mentioned. The db stores the file location and some hash
(e.g size of image) information.

The client is given a list of the images from the db including the hash
information. The client can then download when required each image (as
part of a background thread if connection is slow) to the client and
cache there. It only needs to download the image if the hash
information changes (i.e. it has been updated on the server). This
solution allows for you to seperate the DB from image retrieval (they
could be on seperate machines if required). I used a webservice to
provide the images in question. I used this method as my client server
app can work disconnected, so may not have access to the db all the
time.

Note that the images can also be uploaded by the client using the same
principle.

Hope this helps you decide.
Anthoney
www.nowpromote.com.au