>>>After programming with VFP since 1995, I have finaly decided to solve the problem of a combo box not firing the valid event when it loses focus. I have tested the following and it appears to work fine. Before I add this to my combo baseclass anyone have any comments?
>>>
>>
>>The only time this behavior should occur is with combo.Style = 2 - since this should mean that all list entries are valid input values, and therefore the Valid() is unnecessary.
>>IMNSHO, what should occur for the dropdown list types of comboboxes is that the list should be limited to only valid entries before it receives focus.
>
>One invalid state can exist, with a dropdown list. You have just added a blank record to a table and you require a value to be filled it.

True, but I still wouldn't put it in the Valid() event.

There should be a visible method so the users know what fields are required.
Whether the field's label and/or font is bold, the background color makes it stand out, it blinks (ok, not that <g>), whatever.
Then if they still don't get them all filled in, give them an error that lists the fields they missed and set focus to the first field in the list. I've found that users like this much better.
Even better, if the list is given in another window instead of a messagebox, so they can keep it visible while they make changes.
This from having enough apps where I have to consider the 2 ends of the user spectrum
1) Intimidated by computers - gets even more intimidated if required fields stop them dead in their tracks.
2) Experienced heads down users, where a valid failing won't even be noticed, since they'll assume they got it right all the way through and won't look at the screen until they're ready to save.

Of course, a lot of this is determined by client requirements and such, so my points may be moot. <s>