Termination of Covenants The covenants set forth in this Section 5 shall terminate and be of no further force or effect (i) immediately before the consummation of the IPO, (ii) when the Company first becomes subject to the periodic reporting requirements of Section 12(g) or 15(d) of the Exchange Act, or (iii) upon a Liquidity Event, as such term is defined in the Restated Certificate, whichever event occurs first.
CONDITIONS AND RESTRICTIONS This Recognition of Covenants, Conditions, and Restrictions (this “Agreement”) is entered into as of the day of , 200 , by and between (“Landlord”), and (“Tenant”), with reference to the following facts:
Certain Notifications Until Closing From the Signing Date until the Closing, the Company shall promptly notify the Investor of (i) any fact, event or circumstance of which it is aware and which would reasonably be expected to cause any representation or warranty of the Company contained in this Agreement to be untrue or inaccurate in any material respect or to cause any covenant or agreement of the Company contained in this Agreement not to be complied with or satisfied in any material respect and (ii) except as Previously Disclosed, any fact, circumstance, event, change, occurrence, condition or development of which the Company is aware and which, individually or in the aggregate, has had or would reasonably be expected to have a Company Material Adverse Effect; provided, however, that delivery of any notice pursuant to this Section 3.4 shall not limit or affect any rights of or remedies available to the Investor; provided, further, that a failure to comply with this Section 3.4 shall not constitute a breach of this Agreement or the failure of any condition set forth in Section 1.2 to be satisfied unless the underlying Company Material Adverse Effect or material breach would independently result in the failure of a condition set forth in Section 1.2 to be satisfied.
Modifications and Add-ons Subject to the licensing of the required development rights under separate agreement, Provider shall be entitled to develop Modifications and Add-ons for the Software and shall be permitted to Use Modifications and Add- Ons with the Software in accordance with the license grant to the Software set forth in Section 3.1 herein. Provider shall promptly notify SAP if and when Provider is planning to develop Modifications or Add-ons to the Software. The notification provided by Provider shall include a high level description of the intended functionality and of the timeframe planned for such development. In addition, any Modifications or Add-ons must not i) unreasonably impair, degrade or reduce the performance or security of the Software; ii) enable the bypassing or circumventing of SAP license restrictions and/or provide users with access to the Software to which such users are not directly licensed; and/or iii) permit mass data or metadata extraction from an SAP software to a non-SAP software for the purpose of replacing the Software as the data’s system of record. With regards to the aforementioned item iii), Provider shall refer any Customer requiring such information to SAP.
Modifications/Add-ons 6.3.1 Licensee shall comply with SAP’s registration procedure prior to making Modifications or Add-ons. All Modifications and all rights associated therewith shall be the exclusive property of SAP, SAP Parent or its or their licensors. All Add-ons developed by SAP (either independently or jointly with Licensee) and all rights associated therewith shall be the exclusive property of SAP, SAP Parent or its or their licensors. Licensee agrees to execute those documents reasonably necessary to secure SAP’s rights in the foregoing Modifications and Add-ons. All Add-ons developed by or on behalf of Licensee without SAP’s participation (“Licensee Add-on”), and all rights associated therewith, shall be the exclusive property of Licensee subject to SAP’s rights in and to the Software and SAP Materials; provided, Licensee shall not commercialize, market, distribute, license, sublicense, transfer, assign or otherwise alienate any such Licensee Add-ons. SAP retains the right to independently develop its own Modifications or Add-ons to the Software, and Licensee agrees not to take any action that would limit SAP’s sale, assignment, licensing or use of its own Software or Modifications or Add-ons thereto.
Frustration of Closing Conditions None of the Company, Parent or Merger Sub may rely on the failure of any condition set forth in Section 6.1, Section 6.2 or Section 6.3, as the case may be, to be satisfied if such failure was caused by such party’s failure to use its reasonable best efforts to consummate the Merger and the other Transactions or due to the failure of such party to perform any of its other obligations under this Agreement.
Restrictions on Assignment Unless otherwise provided in the articles or bylaws, a would-be contributor’s rights under a contribution agreement shall not be assigned, in whole or in part, to a person who was not a member at the time of the assignment, unless all the members approve the assignment by unanimous written consent. 2005 Acts, ch 135, §75; 2012 Acts, ch 1023, §157 Referred to in §501A.1001
Conditions and Limitations The admission of any Person as a Substituted Member or an Additional Member shall be conditioned upon (i) such Person’s written acceptance and adoption of all the terms and provisions of this Agreement, either by (A) execution and delivery of a counterpart signature page to this Agreement countersigned by the Managing Member on behalf of the Company or (B) any other writing evidencing the intent of such Person to become a Substituted Member or an Additional Member and such writing is accepted by the Managing Member on behalf of the Company.
Considerations in Assignment (A) The employee shall be granted, upon written request, a conference with the person responsible for making the assignment to express concerns regarding:
Terms and Conditions on Any Consent Any consent or approval that the LHIN may grant under this Agreement is subject to such terms and conditions as the LHIN may reasonably require.
