10 Replies Latest reply on Mar 24, 2017 7:54 AM by FileKraft

    very long opening table

    auarstadtt

      Hello everybody,

       

      Please can you help or give me advices or ideas about this :

       

      I have a table with many fields, some are indexed and now my recor dnumber becomes bigger. On the first opening it take so long to have the record coming.

       

      I would like to know which field takes so long. there is no script trigger on this layout and even on a layout with no field it's the same. So I asume it's a index problem.

       

      Is there a way or a long to know what filemaker is doing for this long time. My concern is that I have some indexed fields which are involved in relationship and I can not de-index.

       

      Thanks for any sugestions or ideas.

       

       

      Antoine Adam

        • 1. Re: very long opening table
          philmodjunk

          Indexed fields should not be an issue for this.

           

          Please describe your layout.

           

          Is this a list or table view so that you get many records listed?

          Are there summary fields on the layout?

          Are their calculation fields that refer to related records in order to compute a value on the layout?

          Do you have other unstored calculations--such as one that uses getNthRecord to refer to other records in the found set?

          Do you have conditional format or Hide Object When calculations that refer to summary fields or aggregate (sum, average, max, list...) data from related records?

           

          These are all things that can slow a layout's update down and is a non-linear function of the number of records in your found set.

          • 2. Re: very long opening table
            Jaymo

            Phil has expertly hit on just about every conceivable slow down possible. If you still can't find the culprit, try duplicating your layout and remove objects until it speeds up. By process of elimination you will know the cause and then be able to address the issue with an alternative approach.

            • 3. Re: very long opening table
              auarstadtt

              thanks for your answer.


              Yes this layout is complex. If there is tab panel can it be on one of the subpanel or it can only be in the first displayed ?

               

              I have to look into all ?

              Kind regards.

               

              Antoine Adam

              • 4. Re: very long opening table
                Jaymo

                Objects on panels not displaying will not cause the slow down.

                • 5. Re: very long opening table
                  auarstadtt

                  thanks !

                  • 6. Re: very long opening table
                    BruceRobertson

                    Yet another problem I sometimes observe involves out-of-context sorting.

                     

                    Let's say  you have a portal on your layout and it is sorted by a field that is in the child record.

                    Again for sake of discussion, the portal contains order items and is sorted by orderItem::productID.

                    But actually, the current layout is based on Salesperson and the portal contains MyOrderItems; including MyOrderItems::ProductID. But the sort order is still based on OrderItems::productID.

                     

                    Does any feature of this layout involve a sort order; and is it the RIGHT sort order in the current context?

                    Maybe the sort order was originally set up wrong.

                    Or maybe it was originally set up correctly; and some feature has been re-purposed.

                    • 7. Re: very long opening table
                      philmodjunk

                      Filtered portals if there are large numbers of related records, can also slow things down.

                      • 8. Re: very long opening table
                        auarstadtt

                        thanks for all this ideas.

                         

                        SQL calculated fields can also or less possible ?

                         

                        Kind regards.

                         

                        Antoine Adam

                        • 9. Re: very long opening table
                          philmodjunk

                          Yes, an unstored calculation field that uses ExecuteSQL could slow down layout updates.

                           

                          Sometimes you just need to keep your found set smaller and avoid things like show all records. If this is a report layout, a script can enter Find Mode first, then change layouts to this layout before performing a Find to produce the report.

                          • 10. Re: very long opening table
                            FileKraft

                            if you have multiple windows open of the same base table and an open (not-committed) record then using an unstored SQL evaluated calculation field can become super slow if there are more then 100 records of this table's total record count (hosted or not).