DoEvents pitfalls

[Guest]

Will someone here educate me a little bit about the pitfalls of using the
DoEvents method?

If I use DoEvents inside a procedure that resides in a library database that
has numerous other databases referencing it. What dangers am I exposed to by
simultaneously running 2 or more of those other (client) databases, calling
the aforementioned procedure?

Hopefully none; because I am creating a WebBrowser control solution, and
there is no way that I have found to avoid errors without the use of DoEvents.

Thanks

 

[Guest]

There is no danger. DoEvents only passes control to windows so other
processes get a turn.