>>>Are you sure that you used the .Object object rather then going directly to the imagelist and to the treeview?
>>>
>>
>>Well, I can't say for sure now :), it was 2 month ago, and I can't repeat the situation, because I have proper comctl32 installed.
>>In January I finished one project in which I was using TreeView, and everything was perfect. When I started new project with the TreeView 2 monts ago, I found that I cannot setup ImageList property, because that combobox is empty. I opened old project and found that this property doesn't work there anymore also.
>>The reason for this odd behaviour was that between those two projects I installed VB5 and automatically got another version of TreeView control.
>>So, since I reinstalled it fom VFP CD-ROM, I don't have any TreeView problems anymore.
>>
>>Nick
>
>But you still shouldn'd rely on the old control, because most likely, other users of your software will have the newer control. For this reason, it's better to set these properties programatically. If your app is only used in-house, you don't have this problem, off course...
>
>Greetings
>Markus

Well, it is difficult to avoid this... :) Like Doug Hennig said in his article about TreeView in June's FoxTalk "...an updated version has a number of problems with VFP 5.0..."
:)

Nick