The client system going into Demo mode in BUSY. what should I do?

If you are experiencing issues with your client system going into demo mode while using an SQL database, you can follow these steps to resolve the issue:
Posibility1: If you are using an SQL database through VAN mode and the client system is going into demo mode, follow these steps:
1. Ensure that port 1433 (or any other port you are using) is open on the main system’s static IP.
2. Open the company in the client system and click on "Set server information" under the company menu.
3. Define the same server name and password in the "Set server information" as defined in the main system.
4. If the issue persists, open the SQL Configuration Manager in the main system.
5. Ensure that BUSY inbound and outbound rules have been created from the Windows firewall.
6. Click on "SQL Server Network Configuration" and then click on "TCP/IP". Define the static IP in the "IP Address" under IP4 and also mention the port in the "IP4 Port" option and "IPAll" option.
7. Restart the SQL services.
8. Reopen BUSY first from the main system and then from the client system and check if the issue persists.
9. If the issue persists, make sure BUSY has been excluded from the antivirus and is running in administration mode.
10. Ensure that UAC (User Account Control) is down in the main system.
Posibility2: If you are using an SQL database through LAN mode and the client system is going into demo mode, follow these steps:
1. Ensure that the main system LAN IP is pinging in the client system.
2. Open the company in the client system and click on "Set server information" under the company menu.
3. Define the same server name and password in the "Set server information" as defined in the main system.
4. If the issue persists, open the SQL Configuration Manager in the main system.
5. Ensure that BUSY inbound and outbound rules have been created from the Windows firewall.
6. Click on "SQL Server Network Configuration" and then click on "TCP/IP". Define the static IP in the "IP Address" under IP4 and also mention the port in the "IP4 Port" option and "IPAll" option.
7. Restart the SQL services.
8. Reopen BUSY first from the main system and then from the client system and check if the issue persists.
9. If the issue persists, make sure BUSY has been excluded from the antivirus and is running in administration mode.
10. Ensure that UAC (User Account Control) is down in the main system.
Posibility3:If you are using the Access database and client system going in demo mode, you can follow these steps to resolve it:
1. First, check the networking in the client system to see if the folder of the main system is being accessed or not.
2. If the folder is being accessed, open the BUSY software and click on "Set data directory." Define the path here using the same path as defined in the main system, but it should start from the server name. For example, if the server name is "A" and the data is defined under C:/BUSYwin/data, then in the client system, define the path as //A/C: BUSYwin/data.
3. Also, make sure that the model is defined the same way in the client system as in the main system. Then, reopen the BUSY software first from the main system and then from the client system. This should automatically enable security for the client system.