A new release is installed by running the new installer over the old one; the configuration is not touched by it. What is worth knowing is what stays and what moves. ## What Stays The configuration folder is not part of the installation. The databases, the [[Invantive Keychain]], the saved grid layouts, the statement history and the licence all live under `%USERPROFILE%\Invantive` and are read again by the new release; see [[Invantive Query Tool/Files and Folders|Files and Folders]]. Where a file format changes between releases, the new release reads the old one once and writes it back in the new format. The statement history is the example: a history held in XML is read once and written back as JSON from release 27.0, so nothing is lost by upgrading and nothing has to be done by hand. ## Which Release Is Installed "About" in the [[Invantive Query Tool/File Menu|File menu]] states the release and the build. That figure belongs in every question: a message code says which component raised a message, and the release says which version of that component it was. The release notes are opened from the [[Invantive Query Tool/Help Menu|Help menu]] and list what changed. ## Several Products on One Device The Invantive products on a device share the configuration folder, the settings file and the keychain. Upgrading one of them therefore changes what the others read, which is deliberate: a database added in the Query Tool is there for [[Invantive Data Hub/Invantive Data Hub|Invantive Data Hub]] as well. Where those products are upgraded at different moments, the older one may read a file the newer one has already converted. Upgrading them together avoids the question altogether. ## Downgrading A file converted to a new format is not converted back. A downgrade is therefore preceded by a copy of the configuration folder, which is the only preparation it needs.