Access 2003 to 2007 Issue - Double-click Event Behaves Differently

[Tony Rusin]

http://groups.google.com/g/e0f7feec/t/1c45efaa366c7d5e/d/4a19dc3df62d5740

From some reason I can't reply to the above thread but I’m running
across the same exact problem.

I have many forms that each have several controls that have a double-
click event tied to them. In Access 03, you double-click in the
control, the string highlights (which is a standard windows function)
and the code fires that opens the form leaving the highlighted string
in the control that was double-clicked on in the background and the
called form in the foreground that now has focus, all as intended.

Opening the MDB in Access 07, you double-click the control and it does
everything above except it’s follow by changing the focus back to the
control that was double-clicked, therefore leaving the called form in
the background, a change in behavior.

Anyone else come up with a solution without rewriting the entire
database?

Thanks,

- Tony

 

[Paul Shapiro]

In the original form control's DblClick event, add this line before
returning:
Cancel = True

I have a note in my code:
Without this, A2K7 SP1 started leaving the focus on the current form
instead of the related form, even though code sets the focus to the newly
opened form.


http://groups.google.com/g/e0f7feec/t/1c45efaa366c7d5e/d/4a19dc3df62d5740

From some reason I can't reply to the above thread but I’m running
across the same exact problem.

I have many forms that each have several controls that have a double-
click event tied to them. In Access 03, you double-click in the
control, the string highlights (which is a standard windows function)
and the code fires that opens the form leaving the highlighted string
in the control that was double-clicked on in the background and the
called form in the foreground that now has focus, all as intended.

Opening the MDB in Access 07, you double-click the control and it does
everything above except it’s follow by changing the focus back to the
control that was double-clicked, therefore leaving the called form in
the background, a change in behavior.

 

[Tony Rusin]

In the original form control's DblClick event, add this line before
returning:
    Cancel = True

I have a note in my code:
Without this, A2K7 SP1 started leaving the focus on the current form
instead of the related form, even though code sets the focus to the newly
opened form.


news:[email protected]...http://groups.google.com/g/e0f7feec/t/1c45efaa366c7d5e/d/4a19dc3df62d...

From some reason I can't reply to the above thread but I’m running
across the same exact problem.

I have many forms that each have several controls that have a double-
click event tied to them.  In Access 03, you double-click in the
control, the string highlights (which is a standard windows function)
and the code fires that opens the form leaving the highlighted string
in the control that was double-clicked on in the background and the
called form in the foreground that now has focus, all as intended.

Opening the MDB in Access 07, you double-click the control and it does
everything above except it’s follow by changing the focus back to the
control that was double-clicked, therefore leaving the called form in
the background, a change in behavior.

That works. Thank you!