Ensure that the following requirements, which apply to the Conquest Runtime and Conquest II, are met and maintained. Note: Updates from Microsoft sometimes revert settings to their default values:
•2 Gigahertz processor or better
•2 Gigabyte of RAM
•100 Megabytes of disk space
•A screen capable of giving an acceptable image at a resolution of 1280 X 1068
•Windows XP SP3 or later, Windows Vista Business or Ultimate SP1 or later, Windows 7, 8 and 8.1 Professional or Ultimate 32 bit or 64 bit. See Microsoft Office for details on discontinuation of XP
•Note: Windows Vista has been described as having deficiencies, especially in 64 bit, that may make it problematic to use with 32 bit applications, which Conquest II is
•A 32 bit ODBC Data Source to a database on an instance of SQL Server 2008 R2 or later
•Note: The compatibility mode of the Conquest database must be set to SQL Server 2008 (100) or later
•MDAC 2.8
•Microsoft Jet 4 SP8. This is used to read connection data from the ODBC DSN, not for data.
•The Conquest Runtime (MS Access 2003 Runtime, which runs out of support April 8th 2014). From Conquest II V2.57a1, the Runtime is obsolete and a preinstall of MS Access 2010 is the recommended method. For more details see Client Side
The user of Conquest on the client machine must have read/write/execute privilege on:
•The folder and sub-folders that Conquest II is installed to, typically their account (%HOMEPATH%)
•The network location of the master library files; “Conquest Reports.mdb” and “UserInterface.mdb”
Conquest users must have read and write permission to the Windows Registry via the functionality of Conquest II. Since the introduction of Windows Vista, Microsoft introduced measures to combat malware, which effectively stop running programs from writing to the \Program Files\ folder structure. The Conquest II installer has been changed to work with this restriction.
Note: Conquest II makes use of the Windows System variables. Changing them could have side effects.
Note: Should Microsoft Updates damage essential components of Microsoft Office, as happened in August 2012, Conquest II may become unusable. Instructions to effect repairs will be provided by Microsoft themselves and require customers to apply them, which may not be easy. Although the configuration of Microsoft Updates and Hot Fixes does not fall within the Conquest Support Agreement, Conquest Support staff may, work load permitting, assist in applying such updates, on an “all care but no responsibility” basis. Once such repairs to MS Access are made, Conquest II will function properly.
Microsoft has published this page to assist customers, who are affected by the August 2012 problem:
http://support.microsoft.com/kb/2687323#FixItForMe
Note: Make sure that all Conquest Mobile Inspection Programs that have been downloaded to CMTPC or CMPPC from the version of the Conquest II database that is being upgraded, have been uploaded. Even if the release notes for CMPPC and CMTPC state that later versions of Conquest II are compatible, they might not be compatible, should a Conquest II upgrade be made between a Download and its corresponding Upload.