5 Replies Latest reply on Sep 10, 2014 12:07 PM by jormond

    What (FM-actions) can cause the server to block/wait for a client?


      Hello experts!


      there are some actions that a user can make (or a developer can code) which cause the server to block other activities while it waits for a client operation to finish. In this time users may see the coffe-cup cursor.


      What exactly are the conditions or actions or script steps, which can cause this?



      Badly programmed CustomFunctions that have an endless loop (Do ALL such CFs cause coffee-cup server-blocking?)

      Or a FileMaker search on complicated non-indexed fields (which are als o not cancelable)

      Or ...


      We would be grateful for your input, as we are keen to identify "show-stoppers" in our solutions.


      Thanking you all


      MrWatson of Günther Business Solutions GmbH