>>>>>>>Come to think of it, you could actually do the same with the free eView -utility and VFP6. In the same vein, while Code Reference is a nice feature in VFP9, it doesn't allow you to edit code, whereas GoFish -utility lets you do that and much more and do it MUCH faster to boot.
>>>>>>
>>>>>>Code References: sure you can edit the found file, just double click on it and the appropriate designer is opened.
>>>>>
>>>>>Well, I'll be dipped. Did this change from VFP8, or has it always been like that?
>>>>>
>>>>>Thanks!
>>>>>
>>>>>Pertti
>>>>
>>>>Always worked that way, I think. Never used VFP 8 all that much, so I don't remember.
>>>
>>>Fred,
>>>
>>>OK, you caught me napping... NOW I know what it was I was thinking of -- I was thinking of the Superclass functionality, not code references. DUH!!!!
>>>
>>>In VFP9 you can VIEW parent class code but not CHANGE it. In VFP6 (and I guess in all of the later versions, too) you can use Ken Levy's SuperCls -utility to go up and down the inheritance chain at will and edit any parent/grandparent etc. in place. I can't imagine why they didn't build that functionality directly into VFP7/8/9...
>>
>>Probably too many memory corruption or other strange issues trying to edit a class that's "in-use".
>
>Begs the question, doesn't it: If Ken Levy could do it without any help from MS (while he was still an ISV and sported long hair and a "Wayne's World" -approach to life), why couldn't MS with their ga$illions of dollar$ do it, too?
>
>Seriously, though, I've been using Superclass for longer than I care to remember, and I haven't seen it corrupt anything, even once. If a class is in use, it tells me so and refuses to co-operate until I release the offending class. I still totally rely on this utility in my day-to-day work. Amazing.
>
>Pertti
>
>P.S. Can you do this trick in .NET, I wonder...

Beats me. If I even try any kind of .NET IDE editting of dependent classes, I crash or lock up the whole thing with alarming frequency.