Standard?  Advanced?  Premium?

If you upgrade and use forms or reports created in previous versions they will be noticeably slower. When going from v4.3 to 2017 I would suggest to create ALL new forms and reports from scratch, don't just convert and use. 

I have had a couple of clients where the network hardware was stepping down their network speed from 1GB to 100MB.  Either an old network card that doesn't support 1GB or a similar issue with a network switch.  Speed difference was drastic even with Sage 100 advanced.

In one case they had an IP phone system where the network cable was run to the phone and then out to the computer.  IP phone only supported 100MB so dropped the speed to the computer.  It would take 30 minutes to do a workstation install!   And then the program ran very slowly.

Thanks all for the replies.

- We're using Sage 100 Advanced

- No custom reports in Crystal. We do our reporting outside of Sage.  So, none of the reports were migrated from prior versions.  Only our check template was recreated.  

- No issues with NIC or hardware -- but good thought.  Machines were all fine prior to upgrade and issues is only with Crystal.  Network latency and transfer rates are great and comparable across machines with and without issue.

I'm still thinking there are some references or missing libraries form prior Crystal versions that are causing the new version to move a bit more slowly when it launches on the workstations with issues.  

Fortunately, SAGE performance has been fine and consistent across all machines.  IT's just the Crystal piece that's killing us! Thanks again for your replies.

Are you using CS-ODBC?  Does enabling / disabling make a difference?  UNC path versus mapped drive?  DNS name resolution?  DEP enabled (there is a Sage KB article on this one)?

When you use the Autorun workstation installer, are you prompted to install any missing pre-req's?  (I've seen silent failures).

Anything in Windows Event Viewer which might give a clue?

If you do an Excel query, avoiding the part where Sage needs to build the work table data, is there a difference in performance?

Are you saying that you create your reports in Crystal outside of Sage 100 and run them outside of Sage 100. Is this correct?

Sorry for the delay.  Not using C/S ODBC.  Haven't tried enabling (was a discussion we had).  Older versions ran so well and latency so low (1-2ms max) that we didn't think it would have much benefit (maybe we're wrong).

Drives are mapped (we did do testing using UNC path as well).

The original install did prompt that some prereqs were missing on most machines. SQL CE and some C++ were pretty common.  

Yes, DNS -- same record we've used for years for the FQDN we use.

- We'll look at Windows Event Viewer.  Should have though of that -- good idea!

- DEP sounds like an interesting possibility.  Do you have the article on this?

- How could we test an Excel query?  We use .Net now to connect  to the API and performance has been excellent (better than older versions).

No.  We have not created any reports in Crystal with Sage.  This is only referring to "canned" or included reports with Sage 100.  We do not use any custom reporting in Sage.  

SP-ITA said:

We do our reporting outside of Sage

But then you posted "This is only referring to "canned" or included reports with Sage 100." Both cannot be true.

Our reporting outside of  Sage is not Crystal -- it's a separate application that uses ODBC (similar to FRx).  For purposes this case, all performance issues with Crystal are with standard reports included with a standard Sage 100 Advanced installation.  Hope that helps clarify.  Thanks