bradyboyy88
Well-known Member
- Joined
- Feb 25, 2015
- Messages
- 562
Hi,
I run a sub routine that does a series of ADO connections to a access database. It is querying and writing to the database. Because of this it is creating a not responding error due to the resources being used and I guess events building up. So I have been researching doevents and was curious what the forums thoughts were on this article of using sleep before using doevents alone?
Avoid Using DoEvents to Wait in Microsoft Access, VBA, and VB6
Anytime before I make a connection and query or write to the database I use doevents so I want to be more informed on the best way to use this.
Also would it be overkill to use doevents back to back before and after connection since I still get not responding most of the time due to the large amount of queries.
Doevents
Connection.Open QueryString
Doevents
I run a sub routine that does a series of ADO connections to a access database. It is querying and writing to the database. Because of this it is creating a not responding error due to the resources being used and I guess events building up. So I have been researching doevents and was curious what the forums thoughts were on this article of using sleep before using doevents alone?
Avoid Using DoEvents to Wait in Microsoft Access, VBA, and VB6
Anytime before I make a connection and query or write to the database I use doevents so I want to be more informed on the best way to use this.
Also would it be overkill to use doevents back to back before and after connection since I still get not responding most of the time due to the large amount of queries.
Doevents
Connection.Open QueryString
Doevents
Last edited: