>Sometime you do. For example in one application I want to display thumbnails of medical images of a given patient. There could be quite a few images per patient. I'll have to download all the images in order to display those thumbnails (LEADTOOLS). Of course there are all kind of solutions you could apply to ease the pain, but they ARE workarrounds.

That's one solution to apply to a problem. So what are you really saying here? VFP wasn't even able to pull BLOB out of SQL Server without major hassles until VFP 9.0 so before that you pretty much HAD to do it the same way by individually retrieving a BLOB via ADO (or raw file conversion).

What you call workarounds may in fact be a better design than what you're doing so it's hardly a workaround. Just because you CAN load up VFP with 20 gig of memory of disk persisted data doesn't mean that you should VFP or not.

>Sorry Rick, but what seems to be a non-issue, might be issues in certain practical circumstances.

As usual we don't agree.