Exactly.

>Gotcha. So default Assign code shows up in sub-classed methods unlike "standard" sub-classed methods, correct?
>
>>Well, no. What I'm saying is that if you go into the properties sheet for the subclass, you see the default code for an Assign, and it doesn't seem to matter if you leave that code in or not for the parent class behavior to work.
>>
>>>Then are we saying it is necessary to add executable code to the method to cause it to override the parent method? If I remember correctly, in previous versions any statements in the subclassed method overrode the parent method, correct?
>>>
>>>>It's a pain in the ass is what it is, but it seems to work whether or not you wipe it out or not.
>>>>
>>>>>Oh wait... even if I wipe it out, once I leave that method and come back it's there again. So I guess it isnt an inheritance problem.
>>>>>
>>>>>>Logic dictates to dump it unless you want your new class to have different behavior. Hmmm...
>>>>>>
>>>>>>>If I subclass a class with a custom property that has an assign method coded, I'm noticing in the subclass the default LPARAMETERS statement shows up. Do I need to wipe that out so it doesn't override the inherited code? Or is it alright just to leave it there? TIA!