what about more practical problems, like having downloading tables that have large memofields or blobs in them ? For example it contains images that could be a several 100K or a few MB each the problem of non disk flushing cursors becomes more obvious very quickly.

You raise a good point on images.

I had to account for this once, and wound up doing it "on demand". A result set might have contained data for 20 signed contracts, but I only brought down the data, not the images of the signed contracts. I had a button in the display interface to only show when the user explicitly said "show me the signed image". (Sort of like when I scroll through my bank transactions....I can view an image of a processed check, but only one at a time).

Good discussion...

Kevin