filemaker pro database design report hang

In comparison, records considered to be “normal” would only take about 1-3 seconds for tabs to load. On these known “slow” patients, users would sometimes have to wait over 30 seconds for the page to load after clicking certain tabs, with most tabs averaging 12-15 seconds. Our client was experiencing significantly reduced response times on some patient records, while navigating from tab to tab. The application is not transactionally intensive, but there are a healthy number of concurrent users - approximately 60 to 70 during peak usage. Offices are located throughout the United States, spread across time zones, though concentrated on the East and West coasts. The environment is a healthcare company using a Claris FileMaker 19 solution in their eighteen offices. Feel free to comment on this post or send us a message through our Contact Form. Then we’d also like to ask YOU … what’s been your experience? We’d love to hear your perspective and results, which will help the entire Claris FileMaker community gain a better understanding of how Top Call logging is best used.

We’ll describe our scenario and observations in the remainder of this article. We recently had an opportunity to make a solid, real-life comparison of Top Call Statistics enabled versus disabled in a user-heavy, multi-office solution. A chance to remove some of the guesswork!

Filemaker pro database design report hang