Sage 100

Sage 100 advanced 2015.04 Business Insights Explorer. User already on Client server ODBC to improve Explorer performance, but today the Customer Payments view is EXTREMELY slow. Even with a 1000 record limit it takes several minutes to come up. In the customer view, with Payments in the lower grid, any customer with more than one or two payments takes 10-15 seconds to update the payments list when switching customers, even though 30,000 customers came up almost instantly in the main view. Any ideas?

No ideas.. only questions.. Was it ever faster in this environment? In my experience this could be 'expected behavior' using Sage Standard or Advanced depending on the record size. It's that darn providex. Is something environmental blocking it (anti-virus, etc.)? Is it workstation specific? Does the table need to be rebuilt (i.e., data)?

It was behaving much better last week ( and for several years before that). I am trying to get the user to test from another workstation, and will do some file rebuilds at the end of the day.

my 2 cents. Our experience has been that any records with a funky date will pull explore views to its knees. (if selecting based on date range) You might try looking at the data for bogus field values in the data record.

Maybe this will help from another thread I posted in (https://90minds-com.socialcast.com/messages/30108939?ref=stream): I addressed BIE performance for a 2014.5 Adv client recently. Initially it wasn't too surprising as many of their data files are quite large, and at least in some cases the data goes back to 2003 therefore I suggested that they would probably benefit by performing some archiving/purging activities. However, it was also determined that creating saved filtered Views in BIE helps with the performance. Along with that, it looks like the ""automatically load data"" setting should be disabled so that the standard non-filtered Views don't attempt to auto-refresh and cause the user to sit and wait. Hence it would seem that we'd ideally want to be able to just go into BIE, have no data appear, and select the saved filtered View to run.

There are some incorrect dates but they are valid (like invoice dated 1934 instead of 2014) but they have been there awhile. Auto load of data already disabled.

I just upgraded a client 2 weeks ago to 2016 Advanced and ran into the same issue. In 2014, the Explorer query runs in seconds. In 2016 at the server it runs in seconds. However, every workstation takes exceedingly long time. We installed CS ODBC and tried Brett's suggestions, all with no luck. The client contacted Sage directly and was told it ""is a bug and being worked on"". That was one week ago. No new information. We will share if we hear something new.

One other thought: System Administrator for another client shared with me that some update from Windows has broken query function for a number of apps which use smb. I am not familiar enough to know if that is a possibility here or not, but have been informed that a number of program developers are waiting for fix from Windows which is anticipated within the month. In the meantime, they have been uninstalling that update from Windows.

Phil is it only the Customer Payments view that is slower? Any chance on the server either ODBC tracing is turned from the Tracing tab or from within SOTAMAS90 DSN on Debug tab?

Rebuild of key and sort files, no joy. No tracing or debug log. Only that view seems to have problems. Cannot verify if the issue started when we applied 2015.04 (had been on 2015.02) recently for Windows 10 support, but it is likely. @CheriOberpriller - might that same bug in 2016 been put into 2015.04?

Finally got here to try another workstation and the data came right up. What could cause one workstation to be slow in explorer?

Since I don't have anyone using Explorer to any degree and at 2015.4, don't have any real insight. But, your latest entry is promising. Hopefully you might be able to see something different about that workstation that will give us all a clue. Maybe that Windows update did impact some workstations but has not been installed on the one you just tested?

Some new insight received today regarding the odbc bug. Apparently the issue is with ODBC and virtual machines for the server. Sage does not anticipate addressing the issue before the end of July.

Changing the name of the workstation got back usable functionality however it does appear that 2015.04 shares the 2016.01 bug of reduced performance in Explorer. It is still running slower on 2015.04 than it was on 2015.02.