Code seems to freeze Access

[coach32]

I have the following code attached to a command button on my Form.
When the button is pressed, the queries should update (which they do) and the
database closes down. The database however doesn't shut down, but when I click
around the database anywhere, it finally vanishes. Is there sonething I need to
include in the code?
Thank you for any advice you can offer.

Private Sub Command29_Exit(Cancel As Integer)
DoCmd.SetWarnings False
DoCmd.OpenQuery "1"
DoCmd.OpenQuery "2"
DoCmd.OpenQuery "3"
DoCmd.OpenQuery "4"
DoCmd.OpenQuery "5"
DoCmd.OpenQuery "6"
DoCmd.OpenQuery "7"
DoCmd.OpenQuery "8"
DoCmd.OpenQuery "9"
DoCmd.OpenQuery "10"
DoCmd.OpenQuery "11"
DoCmd.OpenQuery "12"
DoCmd.OpenQuery "13"
DoCmd.SetWarnings True
DoCmd.Quit
End Sub

[trevor40]

What happens if setwarnings is set to true?
try on error resume next in place of setwarnings = false, 'just the first one, don't use the second setwarnings it does nothing as you are closing the DB

[ItsMe]

Maybe use this instead?

 
Dim db As DAO.Database
Set db = CurrentDb

db.Execute "1"
db.Execute "2"
db.Execute "3"
db.Execute "4"
db.Execute "5"
db.Execute "6"
db.Execute "7"
db.Execute "8"
db.Execute "9"
db.Execute "10"
db.Execute "11"
db.Execute "12"
db.Execute "13"

Set db = Nothing

DoCmd.Quit

It sounds like a RAM issue with the PC that is running the queries. If you still have performance issues maybe you can run the queries off peak hours by dedicating a machine to it and using Task Scheduler to open an Access File.

[Missinglinq]

Access is asynchronous, which is to say, if given a series of commands, it starts to execute one, moves on to the next one and starts executing it, and so forth. It doesn't wait for the first command to be completed before starting the second one. I expect that this is what is causing your problems; you're either outstripping your processor's capabilities, by running 13 Queries, back-to-back, as ItsMe suggested, or one or more Queries depend on values returned by the previous Query. Here's a quick tutorial I've given people who were experiencing this problem:

An example would be a button that runs a series of Queries where all but the first Query is dependent upon the previous Query being completed before it starts to execute. The following VBA code

DoCmd.OpenQuery "QueryA"
DoCmd.OpenQuery "QueryB"
DoCmd.OpenQuery "QueryC"

will immediately run all three, not waiting for one to finish executing before starting the next one. The answer to halting the code in this type of situation is to use DoEvents.

DoCmd.OpenQuery "QueryA"
DoEvents
DoCmd.OpenQuery "QueryB"
DoEvents
DoCmd.OpenQuery "QueryC"

DoEvents returns control to Windows, allowing QueryA to complete running before starting to run QueryB. It then allows QueryB to finish running before starting QueryC.

Linq ;0)>

[ItsMe]

Forgot about DoEvents