>Rick, not sure if I understood correctly, when you say value_assign, is that for a native VFP object, like a textbox? (I assuming it is because of the screenshot you attached in another post)

Correct. If you select an object, and go to Form or Class -> Edit property/method, and scroll down to Value, you'll see that screenshot.

>If that is the case, why using value_assign instead of Interactive/Programmatic change? Furthermore. what happens if you have code in both, the value_assign and the Interactive/Programmatic change? I can see problems there...

They do different things. value_assign is called when the .Value member is being updated by something. You can intercept the source location of where it's being updated, change the value BEFORE it's assigned, etc. And value_access let's you intercept reads. They're both very handy in tracking down where things are updated in a legacy app.

With interactive / programmatic change events, they also work. There's a well-defined order in which the events fire. I had to replicate this order for Visual FreePro, Jr.