File sizes got huge with several thousand 1mb images and splitting over what
was then CDRs was troublesome.
Also, file corruption was a potential problem, plus I liked the ability to
have just the thumbnails archived, was way faster to display a page of
thumbnails and load the file from disk when user double-clicked on a
thumbnail than to convert the blob to a thumbnail then display, and overall
DB performance was way better. Things like DB index rebuilds where faster
etc etc. But this was all with paradox but most of the above would still
apply with dbisam,
I did start converting this app over to dbisam a couple of years back, but I
shelved it when a better project came along.

Cheers
Clive

"Marc Pelletier" <marc@stopspam.goldak.ca> wrote in message
news:Xns97E35CBC6ACDDmmpp1234.dd@64.65.248.118...
> "Clive" <dd@dddd.com> wrote in news:85E7E874-DC7D-4DAA-8654-528887706CB3
> @news.elevatesoft.com:
>
>> I have been down a similar track before.. Firstly storing blobs in a
>> database was not good, what I did was to just store a thumbnail in the
>> database and store a reference to the actual disk file name.
>>
>
> Can you expand on why the blobs in db didn't work for you?
>
> cheers
>
> Marc