Using this app in network is quite handy however the performance relies heavily on always on servers and good networking connections to work, otherwise it will just revert to the local files.
What I propose is that there should be a hybrid solution for faster initialization and overly better performance if accessed by multiple clients, and what I mean by that is this:
The client should synchronise on the first connection to gather the latest stuff from the SQL server, and it should store those connection settings locally, and then either synchronise in the background at regular intervals or manually. This method eliminates
the long initialization process and handles the case of not being able to connect to the SQL server and hence not retrieving any data.