> Actually most of my non visual stuff I do in PRG now. However with a VCX Intellisense kicks in better, as property-comments are shown.

I agree, but you can define property comments in PRG code as well ... although I would agree the syntax is bulky and awkward.

From the VFP 9 "DEFINE CLASS" help topic:

DEFINE CLASS myOLEClass AS Custom

   MyProperty = 5.2

   * Set COM attributes for MyProperty.
   DIMENSION MyProperty_COMATTRIB[4]
   myProperty_COMATTRIB[1] = COMATTRIB_READONLY
   myProperty_COMATTRIB[2] = "Help text displayed in object browser"
   myProperty_COMATTRIB[3] = "MyProperty"  && Proper capitalization.
   myProperty_COMATTRIB[4] = "Float"       && Data type

ENDDEFINE

Finally, I wonder if there's a subtle side effect caused by moving your VFP 8 VCX class to VFP 9? After looking at your code, my hunch is that there's a problem in your VCX tables, not in your code?

Have you tried packing and then recompiling your VCX class?

USE iconbuddy EXCLUSIVE
PACK
USE
COMPILE CLASSLIB iconbuddy.vcx

Great thread!

Malcolm

Srdjan: This thread also gets my vote for thread title of the year :)