In an effort to continuously enhance and improve our product offering, LIM may provide additional releases or versions of its programs in the form of an update as part of our technical support services. It may become necessary as a part of LIM's product life cycle to end the life of a release of a program, and, therefore, LIM reserves the right to EOL its programs. End of Life notices are posted on LIM's website and provided to customers by either mail or e-mail.

When a program reaches an EOL date the program will no longer be supported by the LIM customer support center and an upgrade, if available will be required to receive support services from LIM. In some cases, a product may reach an EOL and will not have an upgrade release. In this case, the product has reached its EOL and will no longer be supported.

Please contact the LIM Support Center so that we can go over the requirements for your business needs. LIM is dedicated to our customers and will work to make these transitions as smooth as possible.

The following has an End of Life (EOL) status:

  • Java API (com.lim.api Package) EOL as of July 1, 2008

    On May 1, 2007 LIM deprecated the Java API (com.lim.api Package) and replaced it with the enhanced Java API (com.lim.mimapi Package).

    There are many reasons to upgrade from the Java API (com.lim.api Package) to the Java API (com.lim.mimapi Package):

    1) Works properly with multiple data types (double, float, integer) across architectures
    2) 100% pure Java. No need to worry about DLLs and .so files for different architectures
    3) Thread safe (using one thread per connection)
    4) Full query capabilities, supporting: P&L queries, queries with multiple reports, and queries with
        multiple blocks
    5) Full writing capabilities
    6) Better exception handling, allowing users to distinguish between network errors and MIM errors
    7) More extensive documentation
    8) New features will be added to the Java API (com.lim.mimapi Package), not to the Java API
        (com.lim.api Package)

    To reference the documentation, see the “Java API (com.lim.mimapi Package)” chapter in the MIM Data and Development Guide.

    For a complete reference to the Java API (com.lim.mimapi Package) code, please see the Java Classes/Interface/Methods javadoc.

    To download the MIM Java API (com.lim.mimapi Package), go to my.lim.com. (Note: If you do not have a my.lim.com account, please contact the LIM support staff.)

     

  • MIMIC Client, Version 3.x and all prior versions, EOL as of June 1, 2009

    The latest version of MIMIC is fully compatible with previously saved MIMIC queries. LIM encourages you to download the latest version.

     

  • XMIM_MATLAB, EOL as of March 1, 2009

    Users now have access to the MIM Java API inside of MATLAB using MATLAB's Java interface.
    Using MATLAB from the Java interface provides enhanced functionality and access to the MIM.
    For the latest instructions on how to use the Java API from the MATLAB environment, see the "MATLAB with Java API (com.lim.mimapi Package)" chapter in the MIM Data and Development Guide.
     

  • XMIM Client, Version 4.x and 5.x and all prior version, EOL as of October 15, 2007

    LIM has developed a Java-based XMIM client that replaces the older X-windows XMIM client application. The new XMIM has an updated, flattened interface so that users can make query selections without having to dig through sub-menus. Many other new features are also available, including a Query Wizard for creating sophisticated event-driven analysis, a new Search Database feature for narrowing searches, a How Do I Say button for help with difficult query phrases and context-sensitive online help. To obtain the current version of the XMIM client software please go to the
    XMIM Download page on the LIM website.


Important Related EOL Notices from Microsoft

The Microsoft Visual Basic 6 Runtime support is EOL, March 2008. The LIM Visual Basic API has dependency on this runtime. Customers are encouraged to plan for this EOL. For more information please see the Product Family Life-Cycle Guidelines for Visual Basic 6.0.

  • Customers that have developed VB6 applications using the MIM Visual Basic (VB) API could port their applications to our MIM .NET API as VB .NET or C# .NET applications.
     
  • Customers that used the MIM Visual Basic (VB) API in conjunction with Excel's Visual Basic for Applications (VBA) should move to the API exposed by the MIM Excel Add-in. For more information, see the chapter "API Calls within LIM Client Products" in the MIM Data and Development Guide.

    Customers also have the option to use MIMICExcel's automatic refresh functionality to pull data into an Excel worksheet. For more information, see the chapter "Refreshing MIMICExcel Queries" in the MIMIC User Guide.


 

 

www.lim.com  Site Map