>>
>> >>>BTW I tried Recompile all,
>> but I guess the P-code is generated when you write the code in the snippet,
>> because when you programmatically change the memo and recompile the
>> project, the new code is not there.
>> >>
>> >>Oh, I didn't try hacking the .VCX, in 3.0 by myself, but may be after the
>> changing you can try to simulate change for that class through Class
>> Designer and then rebuild the project? Sounds weird, but may work. It's
>> good we don't care of it with 5.0
>> >
>> >That's exactly what I'm talking about. If you have a class in a vcx and
>> want to use it in another vcx class, and don't want the user to need both
>> vcx's, copy the class and all its subclasses to the new vcx file. Then go
>> in and "hack" the new vcx file by renaming the classlib for each record you
>> need. Recompilation occurs automatically next time you edit because the
>> time stamp for the vcx and the vct file will be different.
>>
>> That's right for sure. I usually just try to avoid hacking the .VCX until I
>> really forced to do so, by MS for example :)
>>
>> Nick
>
>Nick,
>
>As a fellow Dino let met tell you that VFP is a pain until you start
>hacking. :)
>
>Marc

I am trying to follow Arnon's KISS method (Keep It Simple Stupid) :)