DoCmd.OpenForm takes a long time to load the Form_Load Event (Access 2016)

[justinr12345]

I have a Menu Form. When the User selects the button 'Main' it opens the form 'MAIN' as seen in the code below

Private Sub Command0_Click()

DoCmd.OpenForm "MAIN"

End Sub

The form should ideally leave the DoCmd statement and hit the MAIN Form__Load event immediately. The issue is it takes a few seconds for the code to reach the beginning of MAIN_Load and I am unsure why. Inbetween this time the bottom of Access says 'Calculating . . .' and 'Running Query', although there is no code that requires a query to run when this is called. The RecordSource of MAIN is "SELECT * FROM APN_Status" which is just a table, no query involved. Does it just take a while cause my form is complicated (navigation control with multiple pages, some with navigation controls themselves.)

How can I figure out what is happening between this event??

[isladogs]

Almost certainly the issue is that your form is complex.
As a test, rename it temporarily as something else.
Now create a new continuous form based on that table but without navigation control or multiple pages.
Does it open quickly?
If yes, then you need to review the design of your real main form and try to reduce the number of things that need to be loaded at the start
However if the simplified version loads slowly then something else is the issue - probably the menu form - possibly corruption

One other thing worth trying is decompiling - see http://www.fmsinc.com/microsoftacces.../decompile.asp

[Missinglinq]

[COLOR=#242729][FONT=Arial]

...Access says. . .'Running Query', although there is no code that requires a query to run when this is called. The RecordSource of MAIN is "SELECT * FROM APN_Status" which is just a table, no query involved. ...

I agree that the probable culprit, here, is the Form being so complicated...but note that the RecordSource

"SELECT * FROM APN_Status"

is a SQL statement, and does, in fact, create a Query, from the standpoint of the Access Gnomes...hence the message.

Linq ;0)>