Finding that the response of SQL Estimating is delayed when working with a Windows 10 machine (specifically when modifying a column with grouped items). Here is what we've tried/found so far:
- Working in an environment where the SQL Database is hosted on a virtual 2016 server and is accessed across a physical local network by both Windows 7 and Windows 10 machines (different builds of Windows 10 exist in this network).
- Using SQL Server 2014
- Sage SQL Estimating v19.12
- Found that especially when modifying a column with grouped items, there is a delayed response of the program only at a Windows 10 Workstation.
- No delay from the Windows 7 machines
- Reverted one workstation from Windows 10 back to Windows 7 (so same hardware) and delay went away
- Tested at brand new workstation and delay exists.
- Tested locally at the Server and there is no delay.
- Copied the database and estimates locally to a Windows 10 machine and there is no delay.
- Setup Inbound TCP and UPD ports in the firewall
- Disabled the firewall
- Ran as Domain Administrator
- Ran Sage System Verifier on the workstation
- Changed Role of Estimator to Administrator
We're going to try the following:
- Archiving the Accounting Log Viewer
- Pooling the Timberline Data DSN in ODBC Administrator (as MyAssistant, Timberscan, and ProCore are also used)
- Host the SQL Database on both a Windows 7 machine and a Windows 10 machine and then connect from a different Workstation to test behavior
It seems to me, so far, that this is likely a communication issue between Windows 10 and the server (caching or other) and am searching through Microsoft support as well. I am posting here on the chance that there is another Sage user that has experienced this also.