Skip to content

Device Limitations and Expectations

You are here:
← All Topics

Here is a list of known limitations that currenty exist when using different methods and devices to access the Registry.

Common Performance Limitations

The following factors will influence the speed of searches, rendering the screens and listing records.

  • Your internet speed. Anything under < 8 MB / sec will be sluggish. You can test the speed with Speedtest.Net.
  • Latency: The further you are geographically from the server the slower it could be due to the number of hops (re-routing) in each transmission. Large IT organisations (Google, Amazon etc) overcome this delay by having mirrored / distributed servers scattered around the world so they are closer to the user.
  • Older computers with slower processors, limited ram and graphic processors
  • Attempting to list or sort lots of records.

WebDirect Limitations and Usage Tips

Here is a list of know issues when accessing the Registry via a Web Browser.

  • The behaviour and appearance of the Web app may vary between browsers. i.e.: Chrome, Safari, Edge etc so you could try using a different one to see if it is better.
  • Screen rendering. There may be a delay with the loading of graphics and the screen appearance when resizing and loading windows.  If screens are rendering properly try clicking the ‘Reload’ button in your browser. Unfortunately, you will be prompted again for your login.
  • Non responsive clicks. Web pages and actions activate slower than desktop apps so just SLOW down the navigation and clicks.
  • Active Tabs: The tabs are missing are hard to distinguish between active and inactive states – we are working on it!
  • Many Advanced Functions can only be used via the desktop app and not available for web users. You will see Alerts on this when trying to access certain functions such as:  Saved Lists and Searches, Go Related, Printing Reports.
  • Persistent Login Prompt: The FileMaker server licensing has a user limit on how many users are able to simultaneously connect to the server.  Each web page session uses up a valuable server connection. We have set is a short time-out on the server to close any inactive sessions so that there is enough capacity for other users to login. You will need to keep using the app to avoid the forced logout and conversely please logout when you finish using the app so that other users can login.
  • From our internal tests Google Chrome seems to offer the best user experience on Macs. Safari browser on Mac subject to freezes during fast navigation and frequent login requests.
  • – End –