3 Replies Latest reply on Sep 14, 2014 11:33 PM by JStars

    15 minutes to open a file? Repost

    JStars

      I've been working with a file on a client's server. Friday we imported 30,000 records to one of the tables. The file opens to a layout built on a one-record table (not the one we imported to) with no related records displayed on it. There is no opening script and no script triggers are attached to the layout—but now it takes over 15 minutes for the file to open. The same file opens in 2 seconds on my local machine. What could be going on?

       

      Jonathan Stars

        • 1. Re: 15 minutes to open a file? [Repost]
          RonSmithMD

          What is the connection speed to the server? Examine all the segments first. What kind if sorting if any are you doing and in what kind of fields?

           

          From the iPhone of Ron Smith

          • 2. Re: 15 minutes to open a file? [Repost]
            JStars

            There is no sorting, because there is only one record in the opening table. Nothing about the speed of the server has changed. I duplicated the file and removed the 30k records and put it up on the server, where the two files now run side by side. The smaller file opens instantly, the bigger file takes 15 minutes.

            • 3. Re: 15 minutes to open a file? [Repost]
              JStars

              SOLVED:

               

              There was a cross-table calculation that filled a background image field on the opening layout. I had incorrectly assumed it was a static image. Once I "flattened" the calculation, everything went back to normal. Joshua's post was particularly helpful. At his suggestion I added a completely empty layout with no relationships and closed the file while viewing that layout when it was not being served. That proved there was something on the original layout causing the problem. Then I added one field at a time (there were only 4) until the problem returned.

               

              See the other post here.

               

              Thanks to Joshua Ormond for the tip that solved it.

               

              J **