Nope, but the actual code is a little different. First of all, he has a top level form with a treeview in it. When you click on a node of the treeview, you get one form, then you click on a picklist there, and get a second form. You click on a pick list there, and get a third form. Then, make a change on the third form and click once on the treeview on the top level form. The messagebox telling you there are pending changes shows up and you click on ok then the messagebox telling you there are pending changes show up again. No other clicks are made.

I am going to chalk it up to funkiness between toplevel forms, active x controls, using setfocus in a lostfocus event, etc.

Even putting a nodefault in the lostfocus doesn't work. It still fires twice. If I comment out the setfocus to the last control, it only fires once.

I can see why he has been pulling his hair out.



>hmmm
>
>I tried his experiment and that is not what happened to me. It fires once when I click on the commandButton, and again when I click in the new form (or close the new form). This makes perfect sense to me.
>
>>This seems normal at first, but then, the lostfocus fires again.
>
>This sounds like there is some sort of delay between lostfocus() firing the second time. Are you clicking somewhere with the mouse, causing it to fire again?
>
>BTW, I'm using VFP6 SP5.