Is it possible to turn off MouseMove Event in Access 97?

  • Thread starter Thread starter Kevin Vaughan
  • Start date Start date
K

Kevin Vaughan

Hi,
does anyone know how to turn off the mousemove event once
the mouse is no longer over a control?
I can get it to turn on but do not know how to turn it off.so that I can
reset the changes I made to the controls when I turned it on..

Regards
Kevin Vaughan
 
Kevin Vaughan said:
Hi,
does anyone know how to turn off the mousemove event once
the mouse is no longer over a control?
I can get it to turn on but do not know how to turn it off.so that I
can reset the changes I made to the controls when I turned it on..

I'm not sure I understand you, since you don't "turn off" an event, but
I think you're asking how to recognize that the mouse pointer is no
longer over the control. For that, the answer is to trap the MouseMove
event of the form section (e.g., the Detail section, or Form Header or
Form Footer) that contains the control. Use *that* event to set the
control properties back. Make sure there's enough space between the
control and the edge of the section or of any neighboring controls that
the MouseMove event for the section has a chance to fire.
 
Thanks Dirk,
I had thought about this but presumed that it would slow down the computer
network. I have about 20 command buttons that I need to reset on any
mousemove over the detail section.

Thanks again
Regards Kevin


Kevin Vaughan said:
Hi,
does anyone know how to turn off the mousemove event once
the mouse is no longer over a control?
I can get it to turn on but do not know how to turn it off.so that I
can reset the changes I made to the controls when I turned it on..

I'm not sure I understand you, since you don't "turn off" an event, but
I think you're asking how to recognize that the mouse pointer is no
longer over the control. For that, the answer is to trap the MouseMove
event of the form section (e.g., the Detail section, or Form Header or
Form Footer) that contains the control. Use *that* event to set the
control properties back. Make sure there's enough space between the
control and the edge of the section or of any neighboring controls that
the MouseMove event for the section has a chance to fire.
 
Kevin Vaughan said:
Thanks Dirk,
I had thought about this but presumed that it would slow down the
computer network. I have about 20 command buttons that I need to
reset on any mousemove over the detail section.

Thanks again
Regards Kevin




I'm not sure I understand you, since you don't "turn off" an event,
but I think you're asking how to recognize that the mouse pointer is
no longer over the control. For that, the answer is to trap the
MouseMove event of the form section (e.g., the Detail section, or
Form Header or Form Footer) that contains the control. Use *that*
event to set the control properties back. Make sure there's enough
space between the control and the edge of the section or of any
neighboring controls that the MouseMove event for the section has a
chance to fire.

It won't have any effect on the network, because this kind of processing
is all done on the local PC. It can slow down that PC, though, if you
don't handle it properly. Rather than always setting the properties of
all your buttons in the MouseMove event, use a module-level variable to
identify the control that is currently highlighted, so you need only
reset that control's properties. And in the MouseMove event of the
control, don't bother setting the control's properties if they've
already been set.
 
Thanks again Dirk
Much appreciated
Regards Kevin

Kevin Vaughan said:
Thanks Dirk,
I had thought about this but presumed that it would slow down the
computer network. I have about 20 command buttons that I need to
reset on any mousemove over the detail section.

Thanks again
Regards Kevin




I'm not sure I understand you, since you don't "turn off" an event,
but I think you're asking how to recognize that the mouse pointer is
no longer over the control. For that, the answer is to trap the
MouseMove event of the form section (e.g., the Detail section, or
Form Header or Form Footer) that contains the control. Use *that*
event to set the control properties back. Make sure there's enough
space between the control and the edge of the section or of any
neighboring controls that the MouseMove event for the section has a
chance to fire.

It won't have any effect on the network, because this kind of processing
is all done on the local PC. It can slow down that PC, though, if you
don't handle it properly. Rather than always setting the properties of
all your buttons in the MouseMove event, use a module-level variable to
identify the control that is currently highlighted, so you need only
reset that control's properties. And in the MouseMove event of the
control, don't bother setting the control's properties if they've
already been set.
 
Back
Top