Tim…
---------------------------------------------
Yes we know you are just kidding.
But sometimes in the written word the intention does not come across quite so clearly.
That's the only reason I mentioned it.
In Australia, it is a term of endearment to call someone a clever, devious, old and/or blah, blah, blah bastard. (Except silly old bastard... in which case it is probably a fact, but even then it is almost impossible to offend a
true Australian. [This is one thing that did not come across it the Water Cooler! {So much talk with so little point.

}])
Without knowing your location…you will have a hard time offending me, but you are at liberty to try.
(Having said that, I simply hope like hell I don't offend others… unless of course I try.

)
Back to more technical matters;
The last demo I posted "Four_Hundred_Rectangles.mdb" does not produce screen flicker under my circumstances, A97 and Win2K. But it does do something quite remarkable and/or unexplained.
Under my circumstances if I open the Form everything is as expected. Vast numbers of the Event handler being called as the mouse is moved over the Rectangles.
But that is nothing to this: -
Run the Subroutine that builds the Form.
Open the Form.
Give the computer the 'three finger salute"
Select the Task Manager/Performance Tab"
Move the cursor back over the Rectangles.
The demo shows approx. 1000 Event Handler calls per second.
CPU usage goes to 100% and stays there.
Memory Commit Charge does
not bloat.
Access under these circumstances consumes 100% of CPU time but does not bloat, as it does sometimes.
I have read about the problem concerning the mouse in A97 under Win2K, but this seems like something else again. The reported problem with the mouse in A97 under Win2K is benign. That's fine!
But without knowing the technicalities, it seems prudent to switch off Event Handlers when they are not required.
---------------------------------------------
ghudson…
Good night!
---------------------------------------------
Kind regards
Chris