Using Swisslog in a local network
Although the regular use of Swisslog is using a single computer, Swisslog can also work sharing the database among several instances of Swisslog working at once in a local network. These are the requirements to obtain a good performance:
Minimum 1Gb wired LAN or a 5G WiFi with a transfer rate higher than 800Mb. Don't try 100Mb LAN! Performance is simply unacceptable.
The main instance of Swisslog (which will work as "server") should be installed in the most powerful computer having a SSD disk.
Perfom the following in the computer where Swisslog is installed as "server" (main instance):
Enter folder properties where the Swisslog database is located (default C:\Swisslog\DB) then share this folder giving Read/Write permissions to users from other computers in your network.
Open Swisslog then go to Options and check Enable networking. This will enable the communicattion to other instances of Swisslog installed in other computers. Swisslog sends special commands through UDP messages in port 60009. This is necessary to tell other instances when a new QSO is saved or when you run some functions. IMPORTANT: add exceptions in the firewall of every computer to allow the SwisslV5.exe file all incoming/outgoing communications. Otherwise firewall will block these messages and you won't be able to use the network function of Swisslog.
Now perform the following steps in ALL other computers from your local network:
Install Swisslog in all computers.
Open File Explorer and make sure you have access to the shared folder where the Swisslog database is located in the "server". Example \\RADIOPC\\C\Swisslog\DB.
Once you make sure you have access, open Swisslog then go to File / Open Logbook DB. Select the Swisslog database from the network location (i.e. \\RADIOPC\Swisslog\DB\Swlog_V5.mdb)
Now go to Options and check Enable networking.
If there is UDP communication you will see the number of network users (NetUsers) in the lower part of Swisslog (either in your main instance as in other instances):
The main instance is not counted as network user. NetUsers counts all computers connected with the main instance (the "server"). In the above screenshot means that there are 2 computers connected with the main instance.
Use the more powerful computer as server. SSD is a MUST! I also recommend to use SSD in all other computers. Nowadays SSD disks are very cheap and performace is amazing compared with mechanic disks.
Try to open server instance first. Perform all requested database operations (compressing, resequencing, etc) before open all other instances. This way you ensure the database is optimised before being open by other Swisslog instances.
All functions related to the database (such as saving/restoring a backup, compressing the database or resequencing QSO) must be performed in the server, because they require exclusive use. When executing these functions, Swisslog will inform user that if you continue, other connected instances will be closed automatically.
If you save QSO in realtime into Club Log, eQSL, QRZ, etc, you have to configure it in every instance of Swisslog.
If your logbook contains more than 100K QSO and you use logbook views in your network instances, you should disable Automatic refreshing. Otherwise when a new QSO is entered, this instance will have to read the full logbook to refresh the view and will slow down a lot Swisslog.
I also suggest you to perform LoTW/eQSL synchronization, mass update or intensive logbook operations in the main instance (server). Specially in larger logbooks. DO NOT use other instances while synchronising with LoTW/eQSL. The goal of this function is to be able to use other Swisslog instances in your local network mainly to enter QSOs (multioperators). This is very useful if you have a big shack with different computers with several radios and antennas.
REMEMBER: The more queries to the database from network instances the slower speed you will experience. Because every scenario is different (computer, network speed, number of QSO in your logbook) feel free to make a try to know which functions may affect performance.