Change the Mouse Move Event from 10msec to 1msec

I must agree with Henry, but would like to add that the MouseMove Event is raised by all classes that Inherit from Control, including a Form. This Control Class raises the Event, and unless you could find a way to come between the Control and the RaiseEvent of the MouseMove I do not think there is any way to do this. Perhaps you could write your own Control Class and have it raise the MouseMove Event more often. That would mean you would have to rewrite every Class that Inherits from Control and have it Inherit from your own Control Class. When you are done you have rewritten half of the framework and then Henry's performance issues will kick in ;p

Perhaps an alternative would be to use a timer, set its interval to 1 and check if the mouse is on the control you want it to be and raise its MouseMoveEvent. Of course the Event will be raised twice every 100 milliseconds (once from the timer and once from your actual event). And once again Henry's performance issues will still apply.

All in all I do not think it is a good idea.
Why would you want to check it 1000 times every second anyway? Our eyes cannot even see such movement.

This is one of those strange requirements. Many times, we pick our solutions before knowing fully the problem. I am sure there is a reason why you want to know the mouse events. But before you go in spiral and crash your head, I want you to keep in mind, that the mouse is a *general* purpose input device, as such don't expect nor should you attempt to use it for high resolution solutions.

Take for instance the windows timer, while it server well for general purpose timer, where the precision of some degree milliseconds does not matter, but it is not the right tool for high resolution timer.

If you truly need such high resolution mouse with events and there is very real requirement on your side, then the real solution is not to use Visual Basic (for that matter .NET even by extension Windows events at all). As those are not meant to serve such high caliper resolution, rather general purpose solutions.

While I don't know your problem and I am making a wild guess, you may be ok to use the existing mouse events and see if your problem can be addressed through other means. But again your situation may not be one of those typical ones.

On top of everything else that's been said, you can't even process mouse events that fast to begin with. Getting 1 ms resolution will only fill up the apps message queue to the point where other messages, such as window repaints, won't get processed in time to show the results of your mouse moves. There will be a noticable lag in your UI as the code races to process all the messages that have piled up.

Also, changing the sampling rate cannot be done on an application-by-application basis. That change will affect all other applications running on the system, potentially making it unusable.