Why Would A Combobox Not Process Validate Routine???

Obvious answer - Causesvalidation is false. Of course, if that were the
problem I would not have to post the question. It is set to True and I have
toggled it to False, run the program and then toggled it back to True with no
fix. I have also deleted the Validate routine, saved the code, run it, and
then put the code back.

What I am seeing is that Validate does not fire if I click on a tab or
listbar. These are third party controls so that may have something to do
with Validate not firing. If I click on a textbox the Validate routine fires
perfectly. The problem controls are vbaccelerator controls.

SLink9
Tue Oct 14 09:42:01 CDT 2008

I finally hit on the correct search combo and found a description at

http://support.microsoft.com/kb/230326

Of course, the solution seems to require that the programmer is the one who
created the ATL routine. Since these are VBAccelerator controls I can't use
that fix. Would anyone happen to know if this article applies and if/how I
can use it?

"SLink9" wrote:

> Obvious answer - Causesvalidation is false. Of course, if that were the
> problem I would not have to post the question. It is set to True and I have
> toggled it to False, run the program and then toggled it back to True with no
> fix. I have also deleted the Validate routine, saved the code, run it, and
> then put the code back.
>
> What I am seeing is that Validate does not fire if I click on a tab or
> listbar. These are third party controls so that may have something to do
> with Validate not firing. If I click on a textbox the Validate routine fires
> perfectly. The problem controls are vbaccelerator controls.

SLink9
Tue Oct 14 10:12:01 CDT 2008

The functionality when clicking on the tabset (on the same form) was resolved
by placing the verify routine in the click event of the tab set. That works
fine but I am still trying to get the Validate routine to fire if clicking on
the listbar which is in the parent mdi form.

"SLink9" wrote:

> Obvious answer - Causesvalidation is false. Of course, if that were the
> problem I would not have to post the question. It is set to True and I have
> toggled it to False, run the program and then toggled it back to True with no
> fix. I have also deleted the Validate routine, saved the code, run it, and
> then put the code back.
>
> What I am seeing is that Validate does not fire if I click on a tab or
> listbar. These are third party controls so that may have something to do
> with Validate not firing. If I click on a textbox the Validate routine fires
> perfectly. The problem controls are vbaccelerator controls.

Jan
Tue Oct 14 11:04:46 CDT 2008

SLink9 <SLink9@discussions.microsoft.com>'s wild thoughts
were released on Tue, 14 Oct 2008 07:42:01 -0700 bearing the
following fruit:

>I finally hit on the correct search combo and found a description at
>
>http://support.microsoft.com/kb/230326
>
>Of course, the solution seems to require that the programmer is the one who
>created the ATL routine. Since these are VBAccelerator controls I can't use
>that fix. Would anyone happen to know if this article applies and if/how I
>can use it?

Personally I wouldn't use the validate event at all. It's
far more user friendly to do the validation when the user
submits the form. It's also a lot easier for you.

J


>"SLink9" wrote:
>
>> Obvious answer - Causesvalidation is false. Of course, if that were the
>> problem I would not have to post the question. It is set to True and I have
>> toggled it to False, run the program and then toggled it back to True with no
>> fix. I have also deleted the Validate routine, saved the code, run it, and
>> then put the code back.
>>
>> What I am seeing is that Validate does not fire if I click on a tab or
>> listbar. These are third party controls so that may have something to do
>> with Validate not firing. If I click on a textbox the Validate routine fires
>> perfectly. The problem controls are vbaccelerator controls.

--
Jan Hyde (VB MVP)

https://mvp.support.microsoft.com/profile/Jan.Hyde