MS ACCESS form taking too long to navigate.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • HiGu
    New Member
    • Feb 2012
    • 99

    MS ACCESS form taking too long to navigate.

    I have form1 which has 3 types of something called as WO.Now, when I click on a 'closed WO' form2 opens displaying details.And when I click the back button, it takes atleast 2 minutes to go back to form1.However, this is not the case with Overdue and Open WO and the perfomance is good.
    • form1 has has queries which are run everytime a WO button is clicked.
    • There is more data for Closed WO than that for Open or Overdue WO.
    • form2 dispays detail of only one row from the WO chosen.
    • On click of the back button of form2 it is closed and form1 is made visible.

    Backend is sql server 2005
  • spleewars
    New Member
    • May 2011
    • 13

    #2
    You need to give a better understanding of what is wo.now. apart, does this problem appear out of nowhere?

    Comment

    • HiGu
      New Member
      • Feb 2012
      • 99

      #3
      Hey its only 'WO' and it's the data.There are 3 types of WO or Work Order as it is called.
      I felt this problem could be because there are a lot of rows for closed WO but the problem occurs only when the back button is clicked.

      Comment

      • spleewars
        New Member
        • May 2011
        • 13

        #4
        And a quick question: how many records are in Overdue and Open? Is there a huge amount of records in closed wo?

        Comment

        • dsatino
          Contributor
          • May 2010
          • 393

          #5
          You need to post the code behind the 'back' button on form 2.

          Comment

          • Mihail
            Contributor
            • Apr 2011
            • 759

            #6
            I encounter this problem (very long delay) only for queries that cycle. (Q1 call Q2 and Q2 call Q1). Of course, the chain can be grater than that ( Q1 -> Q2 -> .... Qn -> ... Q1 ).

            Comment

            • Paulo357
              New Member
              • May 2012
              • 18

              #7
              If you anticipate the user will want to go back to Form1 why not minimize it or hide it. close it off Form2 close function

              Comment

              • HiGu
                New Member
                • Feb 2012
                • 99

                #8
                • There's huge amount of data in the production environment for closed WO which could not be executed even in 45mins in sql.
                • When form2 opens,form1 is only made invisible and when back button of form2 is pressed,form1 is made visible and form2 is closed.

                Comment

                • Paulo357
                  New Member
                  • May 2012
                  • 18

                  #9
                  Then what happening is your Form is collating the entire database for the records you require. Try having the Form make a filtered record set to a temporary table a link to that

                  Comment

                  • HiGu
                    New Member
                    • Feb 2012
                    • 99

                    #10
                    How about creating indexes for the columns selected in the query then?

                    Comment

                    • HiGu
                      New Member
                      • Feb 2012
                      • 99

                      #11
                      @Paulo357: How do I do that?

                      Comment

                      Working...