Versions Sample Clauses

Versions. Sage offers different versions of the software. You can use certain versions on a subscription basis, a perpetual license basis, or both. Subscribing to the software gives you access to the most updated version you’ve chosen for as long as you pay the software’s recurring fees; if you don’t, then the software and that data you input to the software will revert to “read-only” mode. Purchasing a perpetual license of the software gives you indefinite access to the version you’ve purchased and the data you input to the software, but software updates require additional fees. Certain of the software’s features and functionality are only available by subscribing. Below is a general description of each version. The specific features and functionality of each version are described in more detail in the software’s documentation. You can find the documentation by visiting Sage 50 features or selecting “About” and then “Help” within the software.
AutoNDA by SimpleDocs
Versions. Your use of the Software under this License may be limited to certain versions, as set forth in the applicable Sales Documentation (for example, a “version plus” license may be limited to certain number of major updates). To the extent your Sales Documentation contains such limitations, your use of versions or releases of the Software that are not contemplated in your Sales Documentation is prohibited and shall be considered a material breach of this License.
Versions. Unless otherwise mutually agreed to in writing, for the Software licensed in Section 8.1.2 or 8.1.3, Contractor must, during the Project, maintain and implement any and all Proprietary Software and Third-Party Software products at their most current version or no more than one version back from the most current version at no additional charge. However, Contractor must not maintain any Proprietary Software and Third-Party Software versions, including one version back, if any such version would prevent the Department from using any Functions, in whole or in part, or would cause Deficiencies in the Module. Any additional costs that are charged by a Third-Party Software licensor or Contractor for an upgrade or Enhancement to a Third-Party Software product or the Proprietary Software are the sole responsibility of the Contractor and will be charged to and paid for by Contractor.
Versions. In the event that BROCADE develops any new features or functionality for (i) of the ASIC Firmware as described in Section 1.1, (ii) the Licensed Software which supports such ASIC Firmware, or (iii) the Hardware versions specified in Exhibit A, and BROCADE makes such new features or functionality generally available to its customers, BROCADE shall offer such new features or functionality to McDATA under the terms and conditions of this Agreement at reasonable prices which are mutually agreed to by the parties.
Versions. NHS Digital shall publish on the Portal: the Connection Criteria and all new versions to apply to each Service from time to time; and details if available of the anticipated changes to versions of the Connection Criteria. Subject to any variation expressed on the Portal, NHS Digital shall for each Service provide Support to the Previous Version of the Connection Criteria for a minimum period of 12 months from the date it publishes the Current Version of the Connection Criteria.
Versions. 5.1NHS Digital shall publish on the Portal:
Versions. For any Included Program that is:
Versions. Unless otherwise mutually agreed to in writing, Contractor shall, during the Project, maintain any and all Third-Party Software products in accordance with the terms of Schedule 1 to Exhibit F (Process to Manage Software Version Currency). The Contractor will provide to the SAC a Software upgrade plan Deliverable at no additional charge for such Services. However, Contractor shall not maintain any Third-Party Software versions, including one version back, if any such version would prevent the Counties from using any Functions, in whole or in part, in accordance with applicable Specifications for the Counties’ then current version of the Systems. Any additional costs that are charged by a Third-Party Software manufacturer for an upgrade to a Third-Party Software product that is not covered by such product’s maintenance agreement shall be charged to and paid for by Contractor as part of its monthly Maintenance and Operations Charges described in Exhibit A, Section 6.
Versions. Unless otherwise mutually agreed to in writing, Contractor shall, during the Project, maintain any and all Third-Party Software products at their most current version or no more than one version back from the most current version and no additional charge, provided that such Third-Party Software version upgrades can be installed and maintained with the Staff proposed in the Response for the Maintenance Services. However, Contractor shall not maintain any Third-Party Software versions, including one version back, if any such version would prevent AOC from using any functions, in whole or in part, or would cause Deficiencies in the System. If implementation of an upgrade to a Third-Party Software product requires personnel in addition to the Staff proposed in the Response for the Maintenance Services, AOC and Contractor shall discuss whether to implement such an upgrade and, if mutually agreed upon in writing, the additional Charges, if any, to be paid by AOC for such upgrade. Any additional costs that are charged by a Third-Party Software manufacturer for an upgrade to a Third-Party Software product shall be charged to and paid for by Contractor.
Versions. This CLA is entered into in Dutch and English versions, the Dutch version prevailing in case of doubt or discrepancy.