Fix for a bug with selecting a syssuperfinfo file

Multiple people have reported an issue with this;

logtruncs failed with: SQL Server message 208, severity 16, state 1, line 1:
Invalid object name 'sysperfinfo'.
DB-Lib error message 208, severity 16:
General SQL Server error: Check messages from the SQL Server

We received this fix from another user.