Everything you do in Access MicrOpay is executed by the SQL Server, so the performance of Access MicrOpay is dependent on the performance of the SQL Server.
The best way to check if your SQL Server is performing as expected is by opening random employee records, which should open within 6-8 seconds.
We recommend isolating the issue and testing Access MicrOpay directly on the SQL Server (temporarily install Access MicrOpay client on the SQL Server and test).
If Access MicrOpay runs the same on the SQL Server, then you know something is wrong with the server, but if it works fine on the SQL Server, then something else within your environment is causing the problem.
Note: Access MicrOpay is data intensive and requires a wired 100mbps LAN connection from the client application to the SQL Server (minimum network bandwidth). As Access MicrOpay maintains an open connection to SQL Server to continually send and receive data as required, latency is a problem – every query is hit with a 100ms delay, which is the time taken for a round trip from client to server and back again.
If using a remote hosting service for SQL Server, the recommended approach is to install Access MicrOpay in the same environment and use RDP to connect remotely to use Access MicrOpay client. Access MicrOpay, as per design, needs a stable and constant connection to the SQL Server, which is why we never recommend using VPN for running Access MicrOpay remotely. We recommended using Microsoft Terminal Services or Citrix for WAN environment.