I wrote my app using .valid() code. Later, I read here that
..lostfocus() is better. Since I am now adjusting that part of the
app, I wish to review this decision.

Big plus to using .lostfocus(): .setfocus() is not valid in
..valid() but is in .lostfocus().

If I simply change the .valid()s to .lostfocus()s, what am I
going to lose? I know that I will lose returning a non-zero value to
determine how many controls forward or back to move, but I do not use
that anyway. Is there any other gotcha waiting to sink its teeth into
me?

Sincerely,

Gene Wirchekno

Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.

Just be sure to include a NODEFAULT in your code in the .LostFocus() where
you do your .SetFocus(), else you'll advance a field past where you expected
to be.

Fred
Microsoft Visual FoxPro MVP


"Gene Wirchenko" <genew (AT) mail (DOT) ocis.net> wrote

Hi Gene,

One could be that LostFocus() takes place later than Valid(),
sometimes even later than nextControl.When(), especially
while navigating by mouse instead of <tab>
Probably rather an advantage than a problem?, just in case
your code relies upon that particular event sequence
somewhere...


-Stefan

"Gene Wirchenko" <genew (AT) mail (DOT) ocis.net> schrieb im Newsbeitrag
news:5dutf0holroh2sp6hh0dbc4m8hl39tdn2g (AT) 4ax (DOT) com...