Hi Ken,
I don't have an answer as to why you're seeing that behaviour, but I'm wondering why you're using two methods to set the the prop.
Why not just put the validation code in the SetMyProp() method and lose the ASSIGN?
>woops - that first paragraph should have said
>
>"The idea is that calling SetMyProp() will "go through" MyProp_ASSIGN for some validation. "
>
>there is no access method involved
>
Roi
'MCP' Visual FoxPro
In Rome, there was a poem.
About a dog, who found two bone.
He lick the one, he lick the other.
He went pyscho, he drop dead!
