>And how do you recommend recovering the image files WHEN the memo/general file gets corrupted? It is much better to store the image (once) as it is in a subdirectory with the relative path stored in the table.(IMNSHO)< G >

I agree. Storing images in a table is a waste of a) diskspace, b) waste
of CPU cycles since you gotta get the stuff out of the database to do
something with it. For Web purposes in particular any way you slice it
files on disk are *much* more efficient.

That leaves only one advantage - portability, which really isn't one
either since the size of a directory structure is likely to be actually
smaller than the size of DB with the same images embedded in it.