///////////////////////////////////////////////////////////////////////////////
//
//  THIS IS PFL182294.TXT
//
//  Copyright :
//    Alaska Software Inc., (c) 2001-2003. All rights reserved.
//
//  Contents  :
//    Installation guide for PFL 182294
//
//  Disclaimer:
//    THIS FILE IS RELEASED AS IS WITHOUT ANY WARRANTY. THE PURPOSE OF
//    A PRIVATE-FIX-LEVEL (PFL) IS TO DELIVER PDR SPECIFIC FIXES
//    OF PRODUCT COMPONENTS TO THE REGISTERED USER. THIS IS DONE BY
//    SUBSTITUTION OF ONE OR MORE COMPONENTS OF THE PFL RELATED PRODUCT.
//
///////////////////////////////////////////////////////////////////////////////


   ___________
   1.0 Preface

   Please note that a Private Fix Level (PFL) covers only those problems
   listed under topic #4.0 in this file. PFLs are released by Alaska Software
   on an irregular basis, depending on the current demand of single or
   multiple customers or a particular 3rd party vendor.

   PFLs do contain special corrections or bug fixes. PFLs are dedicated
   to a specific or a group of specific issues. All changes provided with
   a PFL will be included in the next release of its corresponding
   base-product.

   Please note, a PFL updates only single components of a product.


   ________________
   2.0 Installation

   Before you install a PFL we strongly recommend to make backup copies
   of all components going to be replaced by the PFL. Otherwise you would
   not be able to restore the pre-PFL state at a later point in time.

   You should install the PFL only when you want to resolve one of the
   problems listed under #4.0. If you install the PFL you must replace
   all components included in the PFL. For installation, proceed as
   follows:

   A.) Make sure that no Xbase++ application is running and no
       component of the development package is active.

   B.) Make backup copies of all files listed under #3.0

   C.) If the PFL is shipped as a zipped archive, unpack the
       ZIP archive in the installation root directory.

       Depending on the UNZIP utility it might be necessary to
       unpack the archive with a parameter to extract the files
       into the directories. Please refer to the documentaion
       of the UNZIP utility used.

       I.e. using the UNZIP utility which ships with the Developer
       Subscription CD (<CD-ROM>:\UNZIP) there is no additional
       parameter required and the call looks like

            UNZIP PFLxxxxxx.ZIP

       within the root directory of the Xbase++ and/or XbTools III
       installation.

   D.) If the PFL comes as a self-extracting EXE file, copy
       the file into the installaton root directory of the
       corresponding base product (e.g. D:\ALASKA\XPP32\ and/or
       D:\ALASKA\XBTW32\) and execute it.


   ____________
   3.0 Contents

   This PFL replaces the following components of your Xbase++ installation:

   List of Files:

   XPPRT1.DLL           (Default directory is: \XPP32\LIB and \XPPW32\RUNTIME)
      Xbase++ Runtime Library
      1.82.294

   XPPUI1.DLL           (Default directory is: \XPP32\LIB and \XPPW32\RUNTIME)
      Xbase++ Runtime Library
      1.83.294

   XPPUI3.DLL           (Default directory is: \XPP32\LIB and \XPPW32\RUNTIME)
      Xbase++ Runtime Library
      1.83.294

   XBTBASE1.DLL         (Default directory is: \XBTW32\LIB)
      XbToolsIII Runtime Library
      1.83.294

   ________________
   4.0 Related PDRs

    XPPRT1.DLL
      PDRID:   5256
      SYMPTOM: MemoEdit does not WordWrap correctly 

      PDRID:   5242
      SYMPTOM: MemoEdit hangs, inserting a space + character at EOL

    XPPUI1.DLL
      PDRID:   5284
      SYMPTOM: oXbpMultiCellGroup:SetCell() handles date value incorrect

    XPPUI3.DLL
      PDRID:   5291
      SYMPTOM: XbpOCX does not support WRITEONLY properties

    XBTBASE1.DLL
      PDRID:   209-225
      SYMPTOM: Token behaves different to CA Tools

      PDRID:   209-226
      SYMPTOM: Wrong return value of TokenSep()

      PDRID:   209-227
      SYMPTOM: AtToken() returns wrong values

      PDRID:   209-229
      SYMPTOM: WOM() returns wrong values

      PDRID:   209-230
      SYMPTOM: WoM() returns wrong values

      PDRID:   209-231
      SYMPTOM: NumToken() returns wrong values if one uses 3th parameter

   _______________________
   5.0 Technical Support

   5.1  How to contact Alaska

      You can use either of the following possibilities:

      E-Mail address for customers in Europe, Middle East, Africa:

          support@alaska-software.com

      E-Mail address for customers in America, Asia, Pacific, Australia:

          support@alaska-software.com

      FAX:               (+49) 6196 / 779999-51
      Phone:             (+49) 6196 / 779999-23
      Mail:              Alaska Software Inc., Germany
                         Hauptstrasse 223
                         65760 Eschborn
                         Germany


   5.2  News groups

      The Alaska Software news server address is:

           news.alaska-software.com

      A variety of Xbase++ related news groups are hosted by Alaska
      Software on this server and you are invited to visit our news
      groups regularly. The news groups provide access to a tremendous
      amount of technical know how and experience that is shared between
      Xbase++ users world wide.


   5.3  Knowledge Base

      If you want to know the status or more information about a
      specific issue or PDR, the Alaska Software Knowledge Base
      is a valuable resource for you.

      You may either find out more about a specific PDR given
      its PDR-ID, or also perform a full-text search over
      all articles listed in the Alaska Software Knowledge Base.

      Check it out at the following location:

           http://www.alaska-software.com/kb


   Best regards,

   Your Alaska Software Team