Operating Systems - VantagePoint works on Windows 7 (64-bit), 8, and 10 platforms.
Installation on Windows Server is not supported. Other operating systems (e.g., Macintosh OS X or Linux) are not supported.
- While not a requirement for running VantagePoint, some of our Visual Basic scripts require Microsoft Excel (2003 or later).
Processor - Intel i3 or better, or similar non-mobile processors. The faster the processor, the better the performance. VantagePoint will use multi-core processors to improve performance of many operations.
Memory - The minimum operating RAM is 4 GB, but at least 8 GB is recommended. For most professional versions of Windows, 64-bit VantagePoint can use up to 128GB of RAM, and some versions of Windows allow much more.
The available physical RAM has the biggest impact on VantagePoint performance. VantagePoint files can be quite large, and it is much easier to work with them if they can be loaded into RAM. If the operating system has to use Virtual Memory to load a file into VantagePoint, performance will be slower.
Disk Space - VantagePoint itself uses about 700MB of disk space. This does not include the disk space needed for your data files, which can be quite large - typically no less than 5MB/1000 records.
Since VantagePoint files can be quite large, a fast hard drive reduces the time required to load the file from storage to RAM. Standard drive sizes are usually more than sufficient for VantagePoint file storage. If you are planning to work with large files on a regular basis, it is helpful to have a Solid State Drive (SSD).
Display - Graphical and tabular outputs of VantagePoint require a minimum of 1280 x 720 screen resolution. Many users have told us that having a large monitor (or two) is the best improvement they have made to their VantagePoint experience after adding more RAM.
Data - In addition, VantagePoint requires that you have access to sources of bibliographic data and database definition files for these data sources. Database definition files are available for many popular databases and custom definition files can be coded for virtually any structured text database.