>Sure, you could do that. My instinctive reaction, however, is to go directly to the method that handles the changes. InteractiveChange doesn't fire with every keystroke, BTW. It discards the enter and tab keys, but I understand what you're getting at. Additionally, you look at the value of GETFLDSTATE(JUSTEXT(This.ControlSource)) or OLDVAL(). It is dependent on the situation, however, and these may not be approrpriate in all cases.
>
Right, I see what you mean. I guess really depends on when you want to know what changed. Thanks for the heads up :)
>To paraphase my friend Dragan, "You can do anything three ways in VFP or not at all".:-)
The more I work with VFP the more I see how true that is.
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!
