                  WILEY FIELD TEST 4 README
                  -------------------------

This file contains important information about Wiley.
Information in this file supplements and supersedes
information in the online and print documentation.

TABLE OF CONTENTS
-----------------

1. Installation and Settings
   - Settings
   - Coaches System Requirements
2. Compatibility Issues: Moving from 4.5 to Wiley
   - Creating Tables in an Open Method
   - DataType Property on a Number Field
   - Field Object Names in a Tableframe or MRO
   - Tcursor Functionality after RemovePassword()
3. What's New in Wiley
   - Ease of Use
   - New Sample Application
   - Database Enhancements
   - Performance Improvements
   - Developer Enhancements
4. Known Wiley Problems
   - Crash Bugs
   - Documentation
   - Workgroup Desktop
   - Table Repair Utility (TUTILITY)
   - Experts
   - General


1. INSTALLATION AND SETTINGS
----------------------------

- The default installation places the Paradox files
  and IDAPI files in C:\PDOXWIN. You may change this,
  but if you already have Paradox installed, do not
  install Wiley to the same directory as Paradox, or
  you will overwrite your existing Paradox files.

- The SHARE.EXE command (in either your AUTOEXEC.BAT
  or your CONFIG.SYS) should include these optional
  parameters:

  SHARE /F:4096 /L:400

  The /F parameter allocates file space for the DOS
  storage area used to record file-sharing
  information. The default value is 2048. The /L
  parameter sets the number of files that can be
  locked at one time. The default value is 20.

SETTINGS
- Wiley uses a database engine called IDAPI (formerly
  ODAPI) to access dBASE, Paradox, and SQL tables.
  The IDAPI configuration is stored in IDAPI.CFG.
  Wiley merges your ODAPI settings with IDAPI.CFG.
  Wiley places the new IDAPI.CFG in
  C:\ODAPI\IDAPI.CFG. This is OK.

- In previous versions, the ODAPI directory needed to
  be added to the PATH. You do NOT need to add IDAPI
  to the PATH.

- If you will be running a shipping version of
  Quattro Pro for Windows (which uses ODAPI)
  concurrently with Wiley, set LOCAL SHARE to TRUE in
  the IDAPI Configuration Utility's System Manager
  (System page). If you won't be running these
  products concurrently, don't do this; it will slow
  down performance. The next shipping version of
  Quattro Pro for Windows (which will use IDAPI) will
  not require LOCAL SHARE for use with Paradox for
  Windows.

COACHES SYSTEM REQUIREMENTS
- The minimum system requirements for launching and
  using the Wiley Coaches are:
    Video Resolution: VGA (640 x 480) or higher
    Display:          Grayscale or at least 16 colors
    Mouse:            required


2. COMPATIBILITY ISSUES: MOVING FROM 4.5 TO WILEY
-------------------------------------------------

CREATING TABLES IN AN OPEN METHOD
- A Paradox 1.0 or 4.5 form that creates its own
  bound tables during the Open method will fail to
  run if the tables do not already exist. The failure
  occurs as Paradox attempts to recompile the form,
  due to the change in Paradox version. The compile
  process requires knowledge of a table's structure,
  and the Open method can execute only after the
  compile process is complete. The workaround is to
  create the tables interactively before opening the
  form. Once the form has been opened and saved in
  Wiley, the problem will not reoccur as long as the
  form is opened only in Wiley.


DATATYPE PROPERTY ON A NUMBER FIELD
- A Number field's Datatype property now returns a
  value of "NUMBER"; in versions 1.0 and 4.5 it
  returned "NUMERIC". The workaround is to change
  your source code to reflect the new returned value.


FIELD OBJECT NAMES IN A TABLEFRAME OR MRO
- In some circumstances, you must now refer to a
  Field object in a Tableframe or MRO by including
  the Tableframe or MRO name. For instance, if a
  Tableframe is named CUSTOMER and the field it
  contains is called CUSTID, the code

    CUSTID.MOVETO
  should be changed to
    CUSTOMER.CUSTID.MOVETO

  This is necessary only when you are referring to an
  object in the table from another object in that
  same table, AND the object you think you are
  referring to is not on the current record.


TCURSOR FUNCTIONALITY AFTER REMOVEPASSWORD()
- If a table attached to a Tcursor has a password,
  you must now keep the password in memory as long as
  the Tcursor remains open. If you remove the
  password with the RemovePassword() method, certain
  Tcursor operations such as Locate will fail. The
  workaround is to move the RemovePassword() method
  to the same location as your Tcursor.Close()
  method.


SPEEDBAR METHODS CHANGED TO TOOLBAR METHODS
- All ObjectPAL methods and constants that referred
  to SpeedBars now refer to Toolbars. However, to
  preserve existing functionality in delivered
  applications, the SpeedBar methods and constants
  will remain in ObjectPAL, but undocumented.


3. WHAT'S NEW IN WILEY
-----------------------

Following is a summary of improvements you'll find in
Wiley.

EASE-OF-USE
- COACHES let you use your own data (or sample data)
  while learning how to do Wiley tasks.

- PROJECT VIEWER lists working directory files by
  type. The Project Viewer replaces the Folder. Using
  the Project Viewer, you can
  - Right-click a file name to get a menu of commands
    appropriate to that file.
  - Use the Project menu to add references to files
    from another directory to the list.
  - Change the working directory using the Project
    Viewer text box.

- ONLINE HELP is reorganized and enhanced. New tables
  of contents for each area make the information more
  accessible.

  A new Search All button lets you search for
  information on interactive Wiley, ObjectPAL, and
  Workgroup Desktop topics. Toggle buttons let you
  switch back and forth among the Help systems.

  You can now print multiple topics from ObjectPAL
  Help with one command. For instructions,
  1. From Paradox, choose Help | ObjectPAL Contents.
  2. From ObjectPAL Help, choose File | Print
     Group of ObjectPAL Topics.
  You can use this feature to get a printed copy of
  the new ObjectPAL methods for version 5.0.

  From the IDE Method Inspector, you can now press F1
  to get help on whatever method is nearest the
  insertion point on the selected line. New options
  are available from the Help menu.

- OLE 2.0: Wiley is an OLE 2.0 container in tables,
  forms, and reports. Wiley is an OLE 2.o server for
  tables.

- NEW DESIGN AND LAYOUT DIALOG BOXES give enhanced
  support for screen and printer Style Sheets (.FT
  and .FP files).

- FILE TREE: File selection dialog boxes have
  changed. The Browse button has been replaced with a
  file tree in the dialog box.

- MENUS have been restructured. Utilities, Multiuser,
  and System Settings are on a new Tools menu, which
  also contains Project Viewer and OBEX commands.
  Table and document design and run menus are
  reorganized; some properties and settings have been
  moved to a new View menu.

- TOOLBARS (formerly, SpeedBars) have been
  redesigned. Table, Form (design and run), and
  Report (design only) Toolbars all have a Filter
  button. The Query Toolbar includes a Sort Answer
  button.

- IMPORT/EXPORT does not support Excel 5, but does
  support exporting to the Paradox 4.0 format.


NEW SAMPLE APPLICATION
- Connections is a contact-management application
  developed using ObjectPAL. To start Connections,
  change your Wiley working directory to CONNECT (a
  directory beneath your Wiley system directory), and
  open START.SSL or CONTACTS.FSL.

  Connections includes context-sensitive help that
  you access by pressing F1 from within the
  application. You can also right-click objects
  (buttons, fields, and so on) in the application and
  view their ObjectPAL code by choosing Code Help.


DATABASE ENHANCEMENTS
- FIELD TYPES
  New field types for Paradox tables include:
  Autoincrement     Timestamp
  Long Integer      BCD
  Logical           Bytes
  Time

  BCD and bytes field types are provided mainly for
  compatibility with other database formats that use
  these field types. Some capabilities may be limited
  when you perform operations on these field types
  from Wiley.

  Several fields have new names:
  NEW NAME          OLD NAME
  --------          --------
  Alpha             Alphanumeric
  Money             Currency
  Short             Short Number
  Float (dBASE)     Float Number

- FILTERS
  Filters on tables, forms, and reports are available
  from the Toolbar and menu. Filters on a single
  field are available by inspecting the field and
  choosing Filter. No secondary index is required for
  filtering capability.

- CROSSTABS and 1-D and 2-D summary graphs are now
  available in reports.

- LIVE QUERY VIEWS: A CheckPlus query on a single
  table can return a live query view, if you choose
  this option in the Answer Options dialog box from a
  Query window. Using a live query view, changes you
  make to data in the answer set are reflected in the
  source table. Live query views are available only
  when you use a CheckPlus query.

- AGGREGATION OF EXPRESSIONS is now available in
  calculated fields in forms and reports. This means
  the following calculated field expressions are now
  allowed:

  SUM([table.field1] * [table.field2])
  MIN(SUBSTR([table.alphafield],1,3))
  AVG(cos([table.field]))

  A form can define a custom procedure and then call
  that custom procedure inside of an aggregator, for
  example, SUM(myCustomProc([table.field])).

  There are some restrictions on aggregation of
  expressions:
  - Multiple fields that are referenced in an
    aggregator expression must be from the same
    table.
  - Nested aggregators are not allowed; for example,
    SUM(SUM([table.field]) * 2) is not allowed.

- DATA MODEL files can be saved and reused in forms,
  reports, queries, and in the Data Model Designer.
  The file extension for data models is .DM. You can
  now choose <Data Models> from the File Type list in
  many dialog boxes.

- LOCAL SQL: SQL select statements can now be
  executed against local data. Data definition
  statements can be executed to create tables and
  indexes. Embedded select statements in SQL-ENDSQL
  blocks give ObjectPAL the power of a standard SQL
  query language.


PERFORMANCE IMPROVEMENTS
- We expect improved performance in
  - Report rendering and printing
  - Query speed
  - ASCII import and export
  - ObjectPAL compiling and executing


DEVELOPER ENHANCEMENTS
- IDE: Wiley contains a new integrated development
  environment, with a flexible Debugger.

- METHODS AND PROPERTIES: Wiley contains over 100 new
  ObjectPAL methods, including methods that let you
  define reports on the fly and manipulate the UI,
  and over 200 new ObjectPAL properties. To see a
  list of new ObjectPAL methods, open ObjectPAL Help.
  In the ObjectPAL Table Of Contents, look for the
  heading "New and Changed Run-time Library Methods."

  The word "Changes" in the non-scrolling region at
  the top of an ObjectPAL topic Help screen lets you
  know that changes have been made to that item for
  Wiley. Click "Changes" to see what the changes are.

- A DATA MODEL DESIGNER is available from the Tools
  menu. In the Data Model Designer, you can define
  and use a reference data model as well as the data
  model you're currently working with. You can keep
  the Data Model Designer open while you work in
  other windows.

- You can now pin the Method Inspector by choosing
  Properties | ObjectPAL and checking Keep Pinned in
  the Method Inspector panel of the ObjectPAL
  Preferences dialog box.


4. KNOWN WILEY PROBLEMS
-----------------------

CRASH BUGS
- Using ObjectPAL to import a Fixed Length ASCII text
  file might cause your system to hang or in some
  cases cause a GP error. Importing Fixed Length
  ASCII text interactively does not produce this
  error.

- If you use Drag & Drop while using OLE and try to drag
  something from another application into Paradox, it might
  crash.

- If running multiple instances of Paradox, do not use OLE-
  related dialog boxes (such as Insert Object) in both
  instances at the same time.

DOCUMENTATION
USER'S GUIDE:
- Chapter 5: The description of the time format
  "DBTime" should note that although milliseconds are
  supported by IDAPI, they cannot be displayed in
  Wiley.

ONLINE ObjectPAL REFERENCE:
- Three new ObjectPAL methods have been added to
  control the Project Viewer.
    projectViewerOpen
    projectViewerIsOpen
    projectViewerClose
  
- The new method setMenu is available on both forms and
  reports. It takes a single argument (a menu) and it
  attaches it to a form or report. This method works like
  menu.show() except setMenu attaches itself to the form or
  report you name.

  EXAMPLE
  var
    r report
    m menu
  endvar
  
    m.addText("One")
    m.addText("Two")
  
    r.open("Customer.RSL")
    r.setMenu(m)

  The specified report now knows of this menu and will
  automatically put it back on the menu bar whenever it
  gets focus.
  Menu actions now go to the report, rather than some going
  to the report and others to the form which built the
  menu.

ONLINE HELP:
- Notes in red text are for internal use and will not
  appear in the final version of Wiley.


WORKGROUP DESKTOP
- The Address Book format has changed slightly from the last
  field test release. You must delete any address books
  built with the last field test release and let the
  Workgroup Desktop create a new one.

  Note: The ABIMPORT script will import names from
        4.5 style Address Books.

- Do not enter names that use parentheses in the Alias field
  in the Address Book Manager

- If you install program files on a network, increase your
  network file handles to at least 100.


TABLE REPAIR UTILITY (TUTILITY)
- The Table Repair Utility has replaced the DOS-based
  TUTILITY. To run the Table Repair Utility choose
  Tools|Utilities|Table Repair from the Desktop menu.

- When using the Table Repair Utility, follow these
  guidelines:
  - The table to verify or rebuild must be in the working
    directory.
  - The system setting 'blank as zero' should be set to
    true.


EXPERTS
- Accelerator keys: some key mappings are not correct or do
  not agree with the UI.

- Some UI controls are not yet complete. Some functionality
  is not consistent across the Experts.

- Some runtime errors are not being reported properly and
  might result in a message displayed that has no error
  information.

- In some cases of abnormal exit of the Expert (such as
  after an error) the Expert may not run a second time. If
  this happens, restart Paradox or execute the following
  OPAL code in a script:

       writeEnvironmentString("ParadoxExpertRunning",
       "FALSE")

- The text describing the steps in each of the Experts is
  not yet finalized.

- Printer support is not 100% complete. Experts may not run
  if there are no printer drivers installed.

- Not all links that can be created using the Data Model
  dialog box are reported by the Form and Report Experts.
  In some cases, (such as dBase tables with expression
  indexes), not all possible links will be supported.

- LABEL EXPERT:
  - Although the Label Expert supports Avery Pin-Fed labels
    in this field test release, these labels will not be
    supported in the shipping version.

- FORM EXPERT:
  - The 1:M style with an MRO detail is not working well
    for tables with many fields.
  
  - In some cases, 1:M style with a table frame detail
    creates a table frame that is not sized correctly.
  
- REPORT EXPERT
  - The code to generate a report is not complete. The
    Expert will create a report of the requested size and
    place the tables in the data model.

GENERAL
- When you choose Edit|Undo All Edits with an open
  Editor window, changes are not rolled back if a
  compile or check syntax has been performed.

- To define a picture for a field that will be bound
  and unbound to different tables during runtime, set
  the picture on the unbound field. If you set the
  picture on a bound field it will be lost when the
  field is unbound.

- SQL users: If you are experiencing connection
  difficulties using our ODBC drivers, back up your
  existing driver managers (of the same name) and
  copy these files into the Windows | System
  directory.

- If you run more than one instance of an IDAPI
  client (this includes multiple instances of Wiley),
  you must close them in the reverse order of the
  order you opened them in. For example, if you
  opened A, then B, you must close B, then A.

- In this field test release, comparisons that
  involve blank data can be problematic. It is
  recommended that you set Blank = 0 to True.

- When using OLE with this field test release, it is
  recommended that you use Insert Object rather than
  Paste Link.

- Do not maximize the OLE 2.0 container while
  performing in-place editing. Instead, resize the
  OLE 2.0 container.

- Running a query from the command line does not work
  in this field test release.

                        -----End-----
