F9 System Requirements


Operating Systems Supported

Desktop/Workstation

  • Windows 8.1 and 10 (32 and 64 bit) - F9 V5 only is supported - also for F9 products using PSQL, V12 only is supported on Windows 10 and Windows Server 2016
  • Windows 7 and Vista (32 and 64 bit)

Server

  • Window Server 2016 - also for F9 products using PSQL, V12 only is supported on Windows 10 and Windows Server 2016
  • Windows Server 2012 and 2012 R2 (Note: Server Core installations with WoW64 uninstalled are not supported)
  • Windows Server 2008 (32 and 64 bit) and 2008 R2 (64 bit)

Not supported

  • Windows XP and earlier and Windows Server 2003 and earlier are no longer supported
  • Windows RT is not supported
  • F9 Professional LDI Editor supported on Windows XP

Microsoft Office Excel Versions Supported

F9 V5 and F9 Viewer require .NET Programmability support in Excel. Fully downloaded and installed Click-to-Run versions of Office are supported. Click-to-Run versions that are only partially  installed locally are NOT supported. Office running on the Web is not supported. How to find out if your Excel is Click-to-Run.

  •  Office 365 + Office ProPlus or Professional Plus 2013/2016 with Excel installed on-premise (full installation) (32 or 64bit)
  •  Excel 2016 (32/64 bit) (Desktop Application)
  •  Excel 2013 (32/64 bit) (Desktop Application)
  •  Excel 2010 (32/64 bit)
  •  Excel 2007

Not supported

  • Office Online is not supported
  • Incompletely downloaded/installed versions of Click-To-Run Office ProPlus are not suppported.

F9 Publishing to Viewer Restrictions

  • External links that are parameters of an F9 formula are not supported when published to F9 Viewer.
  • External links that are parameters of an Excel formula (but not within an F9 formula) are supported when published with the Enabled Parameters option only.
How to find out if your Excel 2010 or later is 32 or 64 bit.

Microsoft .NET Framework Requirements

  • F9 Version 5  - .NET Framework 4.5 is required. On some Windows operating systems, .NET Framework must be enabled as a feature within the OS.
Remote Desktop Services/Terminal Server and Citrix
  • Window Server 2016
  • Windows Server 2012 (64 bit) and 2012 R2 (64 bit)
  • Windows Server 2008 (32 and 64 bit) and 2008 R2 (64 bit)
Databases Supported (Dependent on accounting system)
  • Microsoft SQL Server 2005/2008/2008 R2/2012/2014/2016, SQL Express  (Note: SQL Server Native Client ODBC driver is not supported after SQL Server 2012)
  • Providex 5.14.0.0
  • FoxPro 9
  • Oracle 10g, 11g
  • Actian PSQL™ (formerly Pervasive) up to version 12 (client 32 bit). For F9 Report Manager or Scheduler, the "Allocate Resources at Startup" setting in the Pervasive Control Center should be enabled.  Also for F9 products using PSQL, V12 only is supported on Windows 10 and Windows Server 2016
Hardware

Disk space - Individual F9 products typically take up less than 30MB of space on your drive. An F9 Professional installation with Datapump and Actian PSQL combined may approach 300MB.

Memory - This can vary widely depending on the size of the data in your ERP and the functionality you use in F9. The base F9 V5 add-in along with it's dependent components takes approximately 60MB of RAM. For F9 Professional, the base PSQL database engine requires approximately 140MB of RAM. Large amounts of data may add to this value significantly. It is important to understand that the size of the content of your workbooks can be quite substantial in memory and Excel's memory usage can easily dwarf the amount of memory used for F9 itself. These are per-user amounts as well so shared server resources need to be examined carefully to maximize performance.

 

F9 Report Manager Requirements

  • Workstation OS: Windows Vista through Windows 10
  • Server OS: Windows Server 2008 through Windows Server 2016
  • Windows Task Scheduler v2
  • .NET Framework 4.5
  • Excel 2007 SP2 or higher (32 or 64bit versions)
  • F9 Version 5 and/or F9 Viewer installed and configured
  • For ERPs using Actian SQL (Pervasive) databases (this includes F9 Professional implementations), the "Allocate Resources at Startup" setting in the Pervasive Control Center should be enabled.