Updating Visual Studio Tools for Applications (VSTA) whilst remaining on old version of FastStats

A user wanted to confirm that upgrading Visual Studio Tools for Applications (VSTA) on the build and application server to version 16.0.35907.0 and SSMS to version 20.2.37.0 would have any impact on the current installation of Faststats being used:

We confirmed that the versions of the Apteco software being used would be OK with those versions of software from the Visual Studio Tools for Applications 

We did however point out that we look for users to be on software from the last 4 releases (i.e. the last year).  Doing this means that users not only keep up to date with the software and gain use of new and enhanced functionality but also stay within the time period where we do patch issues to old versions of the software.  In general now we would not patch any solutions or corrections back to versions older than 12 months.

• Related Articles

• FastStats Service not producing log files

  The obvious thing to check is that the log file path and file name has been configured and that this exists. It is also worth checking the Log level. If this is set to Warning or Error then it will only write out warnings and errors. Try setting this ...

• Admin User cannot see Users Explorer tab or Licences and Bundles screen in FastStats

  A user who believed they were set up as an admin user, reported logging into FastStats but not seeing either the Users tab or the Administration options. After checking the users settings were correct, we realised that in this case the issue was ...

• FastStats not showing most recent release on splash screen launchpage

  When you run a FastStats Launcher (or FastStats local) then the log in page should show a list of features in the splash page to the right of the log-in panel: If this is not showing the release notes which correspond to the software version (you can ...

• Limits issue within FastStats

  We’ve found and fixed an issue with the query component, where in rare situations we didn’t fully clear the limit properties between queries. This could cause a query limit clause to be mistakenly applied to a subsequent query. To apply this fix: ...

• Cannot access Orbit Audiences in FastStats and PeopleStage

  If the system has been configured correctly then you should be able to access Orbit Audiences from within FastStats and PeopleStage. This is useful because you might have an Audience created within Orbit which you want to refer to in a FastStats ...