Is it possible for Visual Basic to be so busy with tasks as to cause it to miss events?
I ask because this is my situation:
I have two projects. One is nothing but a form, with some functions that raise an event. When I run this program, the event always triggers as it's supposed to.
The other program has the identical code that generates the event but has many other items on the form, such as timers controls, etc.. When I run this project the event doesn't fire as it should unless I repeatedly click the command button that I'm using to test the event. Is there a way to "force" VB to look for events? or maybe stop what it's doing and watch for an event for, say , 2 seconds?..
I realize this question is general. I have source code if anyone is interested but I'm hoping I don't have to do that..