I haven't used this class myself, but I've made a search using cImageList in Code Reference and I found it's used in cImageListLoader as a cClass property. It also has this strange property
=IIF(VFPVERSION()<6, "58DA8D8F-9D6A-101B-AFC0-4210102A8DA7","2C247F23-8591-11D1-B16A-00C0F0283628")
for cClassID.
So, it could be that new version of VFP doesn't have this classID and class anymore. Just try to search registry for this entry....
>This has probably been answered before, but I cant find info. I have a MM app/form that loads a TreeView and Imagelist control for navigation. It has worked flawlessly with VFP 6 and 7, however since recently upgrading to VFP 9 SP1, it crashes on the following line:
>
>IF llOK
> *-----------------------------------------
> *--- Add the ActiveX control to the Parent
> *-----------------------------------------
> .Parent.AddObject(.cNewObjectName, .cClass, lcProgID)
>ELSE
> .
> .
> .
>
>This = ImageListLoader
>.cNewObjectName = "ImageList"
>.cClass = "cImageList"
>lcProgID = "MSComCtlLib.ImageListCtrl.2"
>
>The error message is "Class definition cImageList is not found"
>
>In reading VFP 9 help, it indicates that I should save a subclass of the ActiveX control to a VCX library. I am not sure what is meant by this. Also, would changing the base MM Framework class to use NewObject()instead of AddObject be a better solution? Thanks for any help
If it's not broken, fix it until it is.
My Blog