PRB: Form's MouseMove Event Is Not TriggeredArticle ID: Q116388Creation Date: 20-JUN-1994 Revision Date: 01-DEC-1996
The information in this article applies to:
SYMPTOMS
Moderate: Requires basic macro, coding, and interoperability skills.
An event procedure assigned to a form's MouseMove event is not triggered as
you expect it to be.
CAUSE
A form's MouseMove event is triggered only when the mouse pointer is
positioned outside the boundaries of any sections or controls on the form.
RESOLUTION
To trigger a MouseMove event within the boundaries of a section on a form,
assign the event procedure to the section's MouseMove event, not to the
form's MouseMove event.
MORE INFORMATION
A form's MouseMove event is triggered only when the form's window is sized
to be larger than the form itself, and the mouse pointer is positioned
outside the form but inside the form's window. This can be useful in
instances where the form has been maximized, and it is necessary to
determine if the mouse pointer is positioned outside the normal boundaries
of the form. In most cases, though, it is more useful to trap a MouseMove
event that has occurred for a form's detail, header, or footer sections.
|
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.