compiling queries

I noticed when starting from a blank database and importing in many queries from an older database the forms are terribly slow when opening. I think I found the reason but still need a little help. It seems since the queries have never been opened the have never been compiled. If I open them, show the data, then close, the forms seems to open faster.

If this is the case is there a way to open and close or compile all the queries in vb?
LVL 1
ShawnAsked:
Who is Participating?
 
Jim Dettman (Microsoft MVP/ EE MVE)Connect With a Mentor PresidentCommented:
That is correct.  This occurs after a compact and repair as well.

What's happening is that the plan for query execution is being generated and saved.

I don't have code off-hand to open and execute every query, but for the most part, you could do it in VBA.

However it would depend on the queries and how they were writen as to how easy or complete it would be.

 What you would need to do would depend on the type  (action, select, pass-through), what they are doing (ie. tied to a form), and if they must be done in sequence (ie. make table, then appends after that).

Jim.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
"If I open them, show the data, then close, the forms seems to open faster."

That is because the JET query execution plan is recreated based on current datasets. So, effectively - you have 'recompiled' the queries.

"If this is the case is there a way to open and close or compile all the queries in vb?"
I'm thinking if in vba, you open each QueryDef and then save/close ... this may do the same thing.

mx
0
 
Rey Obrero (Capricorn1)Commented:
the first time the query executes, the query will be compiled, then the compiled query is used when the query is executed.
0
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Maybe something like this (make a backup first).  I just tried this - but I have no way to tell on this system if it makes a difference.

    Dim qdf As dao.QueryDef
    Dim db As dao.Database
    Set db = CurrentDb
    For Each qdf In db.QueryDefs
         Debug.Print qdf.Name
         On Error Resume Next  ' in case query has systax error, like some of my EE qrys.
        qdf.sql = qdf.sql
        Err.Clear
        qdf.Close
    Next qdf
   
    Set qdf = Nothing
    Set db = Nothing
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<I'm thinking if in vba, you open each QueryDef and then save/close ... this may do the same thing.>>

 Has to be a open of the query def, modification of the SQL, a save, and then a execute of the query without a save after that to force a re-compile.

Jim.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
"a save"
So how do you actually 'save' in vba ?  Say relative to the code I posted.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
There's no code equivalent.   Just setting the property seems to be enough, although it may be when it goes out of scope or is closed that the save actually takes place.  I've never really pinned it down.

 When I answered though, I was thinking of the steps I'd do manually, so I really didn't answer that correctly.

 A execution is required though, which is where doing this in code becomes a problem depending on how the queries are written.

Jim.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Execute - yeah, that's what I suspected - and yes, problematic in code most likely.

The good news: Compact & Repair.

mx
0
 
ShawnAuthor Commented:
does Compact & Repair really compile the queries though?
0
 
Jim Dettman (Microsoft MVP/ EE MVE)Connect With a Mentor PresidentCommented:
<<does Compact & Repair really compile the queries though?>>

  It doesn't compile them.  What it does is flag them as not compiled, so first time they are run, they are re-compiled.

 That's one of the reasons I've never bothered with trying to compile all queries before I deliver something...it's just not worth the effort.

Jim.
0
 
ShawnAuthor Commented:
>>so first time they are run, they are re-compiled.
even when theyare behind a form or do they still have to be run/opened directly?
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<even when theyare behind a form or do they still have to be run/opened directly? >>

 That was my point earlier; many won't run outside of a certain situation, such as a form being opened.

Jim.
0
 
ShawnAuthor Commented:
ok, thanks Jim. You just saved me a lot of time. :-)

Shawn
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Connect With a Mentor Database ArchitectCommented:
"even when theyare behind a form "
I believe they are still flagged for recompile (after a C&R) since they do appear in the QueryDef collection - show as (example):

~sq_ffrmLstBox

Thing is ... since C&R only flags queries for recompile ... this may be why - you experience slowness - at various times - when a given query is actual recompiled upon first use after a C&R.  However, how today's machines this may be so fast that is't negligible - probably hard to measure/determine.

mx
0
 
ShawnAuthor Commented:
thanks for helpin g me understand. So solution is we don't need vb but a C&R. C&R sure comes in handy.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.