I can think of two (non-kludgy IMHO) approaches--

1. Custom method that does whatever your rightClick event does. IE .popUpForm(). The RightClick event would call this method, and the valid event would call this method when it has found an invalid entry. The valid could then check the new value.

2. In the valid, if there's an invalid entry, revert the invalid entry and return 0 (or .F.)

I would leave the actual implementation up to you < g >. But the problem isn't really the firing sequence of the right-click and valid event so much as that you "leave" the field when you pop up the entry form.

BTW, sounds like a nice interface. Does your user like it?

>I have a textbox with code in the RightClick and the Valid Events. The user can right click on the field to display a form with a list box of valid selections. The user can also key directly to the text box and the valid event will compare againt the same list. This is very similar to the fuctionality of a combo box, but the user did not want a cobo box for this field.
>
>Anyway, if an incorrect value is entered, an error message is displayed by the valid when you attempt to leave the field. If I try to right click to select a correct entry, the valid event fires first, then displays my right click form, then returns to the original form leaving the right click form burried underneath.
>
>In the valid event, can I check to see if the user right clicked? That way I could suppress the error message since they are attempting to fix it, not just leave the field.