If the discussion here is anything to go by then it is a known bug with the MouseDown event. And the "Paul_Hossler workaround" is the only workaround if you are bent on using it!