If you are currently using AcctVantage 2015 or older, you need to contact AV Support before installing AV 2017.

There is no need for a new key file if you are already running AV 2017.0.x.x.  If you are upgrading from an older release, please contact Support to obtain your license key.

****AV 2017.0.0.3  December 19, 2016....If you are upgrading from a previous AV 2017 Version, you MUST also download and install the current AV 2017 Client on each user's computer****  It is unusual to require an AV Client side upgrade in the same series, but is necessary this time.

Click this link to download the current AcctVantage 2017.

Note that there are 4 installers -- AV Server Mac & Windows and AV Client Mac &

Installation Instructions

AcctVantage ERP Client Install Instructions (Mac OS)

AcctVantage ERP Server Install Instructions (Mac OS)

AcctVantage ERP Server Install Instructions (Windows)

It is very important to make sure that your Data File is backed up regularly. This lesson details how to set the Preferences for your data backups. If you want restore from a backup see the lesson Restore From a Backup File.

Here are some strategies for ensuring that a backup file is available in the event that one is needed:

1. Scheduled backup (This is the primary topic of the lesson below): We recommend scheduling a backup to occur at least once a day. Typically the best time to do this is overnight (or some other time when everyone is out of the system).
2. Backup before posting transactions: This is a good way to make sure that you always have a current backup available. There is a check box available on the Post Transactions screen that you can mark to run a backup when posting. However, if you often post individual records using the Action Menu, then additional backup strategies become even more critical.
3. Backup before importing data: Backup before any import of data is attempted in Acctvantage. This includes GL imports, Physical Inventory imports and XML imports.
4. Implement company-wide backup procedures: Most companies have standard backup procedures in place for their computer systems. We do not intend for any of the above procedures to replace any company-wide procedures. We highly recommend implementing and/or continuing any procedures for routinely backing up all company data.

Notes:

• The built in AcctVantage ERP backup scheduler will backup your AV data file to the designated location.
• It does not backup any other files on the hardware and should not take the place of a general system wide backup.
• Your staff or 3rd party IT support should have backup plans in place in case of a hardware or other failure.

Below are bare minimum system requirements for both AcctVantage Client and Server hardware. Better than minimum hardware will improve performance.

AcctVantage Technical Support does not support hardware, network, or other IT setup outside of actually installing and configuring the AcctVantage software. However, we will be happy to work with your IT staff or consultants to discuss our experiences with various hardware/network situations.

-----------------------------------------------------------------------------

Notes on Operating Systems:  

• AcctVantage releases are certified to work with specific versions of Macintosh and Windows Operating Systems.  
  • For Macintosh, certifications are done at the 10.x level, meaning that an AcctVantage version certified for 10.5 or earlier will not operate on a server or client running Mac OS 10.4.  
  • For Windows, the certification is done by major release version such as Windows XP or Windows 7.
• We suggest turning OFF all Automatic Update programs that may update an Operating System version. The OS certification applies to both Server and Client machines.
• Bookmark this article for the latest supported OS versions and the corresponding AcctVantage release.
• AcctVantage operates on a Local Area Network (LAN) using TCP/IP protocols. If all users are on the same LAN, then dynamic IP address assignment is acceptable. It is recommended that all LAN connections be routed through switches rather than hubs and that “daisy-chaining” of switches and/or hubs be avoided.