Sergey

Yes, I understand that

--
Fabio is asking about loading images from blob filed into ImageList control to use in TreeView, ListView, e.t.c.
---

I am aware of that. That is why I said:

---
I understand that you're saying you want to load it into a listbox, fine, but a listbox picture property doesn't take an object reference, right? It takes a filename. (or have I mis-remembered this? it's been a long time <g>)
----

AFAICS the point of adding blob fields into the product had nothing to do with making the use of specific ActiveX controls different from how you would have used them previously. IOW, you used filenames with these controls before and you would continue to use filenames now.

It would be nice (and there's every chance it was considered), but it just wasn't a main goal of having blob as a data type. AFAICS the point of having blobs was simpy to synch up with SQL Server datatypes.

Another way to look at what they might have done (a little different from the LOADPICTURE() approach) would have been to provide some sort of CAST() option so that you could take an instance of the VFP Image object, with its blob loaded up in PictureVal, and cast it to the right type of object to be added to the ImageList control's collection. As I said, it would be nice, and it was probably considered.

But there are lots of reasons to use FoxPro for middle-tier data handling that don't go near ActiveX controls. So there is nothing "demential", to use Fabio's creative terminology <s>, about their having done one thing and not the other.

>L<