
                      WILEY FIELD TEST 1 README
                      -------------------------

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

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

1. Installation
2. What's New in Wiley
   - Ease of Use
   - Database Enhancements
   - Performance Improvements
   - Developer Enhancements
3. Changes to the IDE
4. Known Wiley Problems


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

- The default installation places the Paradox files and
  IDAPI files in C:\WILEY. 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 Minimum Install option does not yet work correctly. If
  you don't want to install all the Wiley files, choose
  Custom Install to select the ones you want to install.  Custom 
  Install might not indicate correctly how much space you need
  for the files you want to install.

- The [OBEX] WORKDIR entry in the WIN.INI file tells OBEX
  where to find the OBEX.INI file. Do not delete the OBEX.INI
  file; if you do, you will have to re-enter account
  information; even so, the pointers to the ObjectStore and
  AddressBook may not match any existing databases.

  It is suggested that you make backup copies of your existing
  Obex files, Object Store and OBEX.INI files before you install.
  
  Install places OBEX files in a subdirectory under the
  directory where Wiley is installed. Do not attempt to
  override this location. 

  Install creates a new version of the Workgroup Desktop and 
  OBEX without changing your current files. Your WIN.INI
  file is updated to point to the new Workgroup Desktop and 
  OBEX. If you want to use your existing Workgroup Desktop or
  OBEX, modify the WGDIR entry in the PDOXWIN group or the
  OBEXDIR entry in the OBEX group of your WIN.INI.

- After the installation of Wiley is complete, you may find
  that a \BORLAND.TMP directory has been created off of your
  Windows directory. This directory, and all files in it,
  may be deleted.  This problem will be resolved in the final
  shipping version.

- The Wiley install does not currently install a configuration
  file to match the Windows country language and code page.
  If you want to use a different configuration file, copy the
  appropriate file from your Paradox 4.5 directory into your
  Wiley directory. Then, use IDAPICFG to open the alternate
  configuration file, and save it as IDAPI.CFG.

- When Wiley is installed, it updates the [PDOXWIN] section
  in the WIN.INI file to set new working and private
  directories. These working and private directories will be
  used by default for both Paradox 4.5 and Wiley. Paradox 4.5
  and Wiley also share the PDOXWIN.INI and PDOXWORK.INI
  files.

- When Wiley is installed, it updates your Windows file
  associations. This means double-clicking a .DB, .SSL, or
  other Wiley file launches Wiley.

- 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. IDAPI does NOT need to be added to the PATH.

- If you will be running Quattro Pro for Windows 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.
  
- NETWORK INSTALLATION
  For information on installing Paradox on a network, see the
  NETINST.TXT file, located in your Wiley directory.


2. WHAT'S NEW IN WILEY
-----------------------
Following is a brief summary of improvements you'll find in
Wiley.


EASE-OF-USE
- INTERACTIVE TUTORS let you use your own data while
  learning how to do Wiley tasks. (You can also use sample
  data.) Click the Interactive Tutor SpeedBar button to 
  see a list of tutors.

- PROJECT VIEWER lists working directory files by type.
  Right-click a file name to get a menu of commands relevant
  to that file. Use the Project menu to add files from another
  directory to the list (the files are not moved into the
  working directory; only a reference is created). You can
  change your working directory in the Project Viewer text
  box. Click the Project Viewer SpeedBar button to open the
  Project Viewer. The Project Viewer replaces the Folder.

  When you start Wiley, the Project Viewer is open on the
  Desktop. If you want the Desktop to be empty upon startup,
  open the Project Viewer, choose Properties | Project, and 
  uncheck the box next to "Open Project Viewer on Startup."

- ONLINE HELP
  a) Help is being reorganized and enhanced. New tables of
     contents for each area will make the information more
     accessible. Many are already in place. Tables of contents
     are expandable and collapsible and divide topics into 
     logical categories.  Documentation in online Help covers 
     many of the new features and changes in Wiley, such as OLE2
     support, filters, the Data Model Designer, the Project Viewer,  
     and many of the new ObjectPAL methods.


  b) A new Search All button lets you search for information 
     on both interactive Wiley and ObjectPAL topics. Toggle 
     buttons let you switch back and forth between the two Help 
     systems. 

  c) You can now print multiple topics from ObjectPAL Help
     with one command. For instructions,
     1. Open the ObjectPAL Help contents screen.
     2. Click "Print ObjectPAL Reference Topics" (under
        the heading "Help Tools").
     You can use this feature to get a printed copy of 
     the new ObjectPAL methods for version 5.0.

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

  e) You can now close Help by pressing Esc.

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

- REPORTS and FORMS
  a) New design and layout dialog boxes give enhanced support 
     for screen and printer Style Sheets (.FT and .FP files)
     and a live preliminary design area.

  b) The Calculated Field text box in the Define Field
     dialog box now dynamically sizes up to the width of
     the dialog box.

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

- Many MENUS are 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 are moved to a new View menu. 

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

- These revamped DIALOGS offer additional options:
  a) Properties | Answer Options from the Query window
  b) Properties | Desktop... (includes preferences for
     forms and reports and the system font)

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


DATABASE ENHANCEMENTS
- NEW FIELD TYPES for Paradox tables:
  Autoincrement
  Long Integer
  Logical
  Time
  TimeStamp
  BCD
  Bytes

  BCD and Byte 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 and forms are available from the SpeedBar
  and menu. Filters on a single field are available through 
  inspection.
  Filters are available to reports, letting you print only the
  records you want to see.
  No secondary index is required for filtering capability.

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

- LIVE ANSWERS:  A CheckPlus query on a single table
  can return a live Answer, if you choose this option
  in the Answer Options dialog box in a Query window. 
  With a live Answer, changes you make to data in the
  Answer table are reflected in the source table. Live
  Answers are available only from a CheckPlus query.

- FORMS and REPORTS:
  Now allow aggregation of expressions.
  This means that the following kinds of calculated field
  expressions are now legal:

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

  There are some restrictions on this capability. First,
  when multiple fields are referenced in an aggregator
  expression, they must be from the same table.
  Second, nested aggregators are not allowed, for example,

    SUM(SUM([table.field]) * 2)    is categorically illegal.

  A form can define a custom proc and then call that
  custom proc inside of an aggregator, for example,

    SUM(myCustomProc([table.field]))

- DATA MODEL files can be saved and reused in forms, 
  reports, queries, and 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
Expect improved performance in
- Report rendering and printing
- Query speed
- ASCII import and export
- ObjectPAL compiling and executing


DEVELOPER ENHANCEMENTS
- IDE: New integrated development environment, with a
  flexible Debugger. This is not documented in online Help;
  See the next section in this file for information.

- Over 100 new ObjectPal METHODS and over 200 new ObjectPAL 
  properties, including many methods that let you define reports
  on the fly and other methods to manipulate the UI. To see a 
  list of new ObjectPAL methods, open ObjectPAL Help. In the 
  ObjectPAL table of contents, look for the heading "New Methods
  Listed by Version Number."

  Once you're in an ObjectPAL topic screen, the word "Changes"
  in the non-scrolling region at the top of the 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.


3. CHANGES TO THE IDE
---------------------
There are many new features and changes to the Integrated
Development Environment for Wiley. Following is a brief
summary of some these changes.

- ObjectPAL Preferences Dialog box
  In a Form Design window, choose Properties|ObjectPAL to set
  preferences for ObjectPAL and the IDE. You can also open 
  the ObjectPAL Preferences dialog box from the Debugger by 
  choosing Properties|ObjectPAL.

  The preferences you choose are saved when you exit Wiley.
  Windows and window behavior persist between sessions.

- Developer menu
  Check Developers Menu in the ObjectPAL Preferences dialog 
  box to turn on the special developer menu in the Form Design
  window. The Developer menu adds the Program menu and additional
  commands to the View, Properties, and Tools menus.

  If you choose Developers Menu, the Properties menu includes a
  Compile with Debug command that takes the place of the Enable
  DEBUG Statement menu command.

- SpeedBar changes
  The Check Syntax button has been replaced with the Compile and
  Compile All buttons (and menu commands on the Program menu).

- Watches
  You can now Add a Watch to a variable in the Editor, and keep track 
  of the variable's value in a Watch window while the form or method 
  runs.

- Modal windows
  The Watches, Breakpoints, and Tracer windows are modal, remaining
  open until you close them. Right-click inspectors are available
  in all IDE windows.

- Redesigned Methods Inspector
  Check Keep Pinned in the ObjectPAL Preferences dialog box to pin the 
  Methods Inspector to the Desktop. When pinned, the Methods Inspector
  lists the currently selected object. You can shift-click multiple 
  methods and open or delete the selected methods from the inspector
  menu. You can also use the inspector menu to create a new method 
  or get Help.

- Editor window
  The Editor window you had displayed when you ran a form is
  opened upon returning to the Design window.

- Editor ObjectPAL menu 
  Right-click anywhere in the Editor to display a special ObjectPAL 
  menu. Ctrl-N is Next Warning (in the editor only).

- Set Breakpoints and Watches in the Editor or Debugger
  You set Breakpoints in the editor or debugger. Use Ctrl+B or 
  Ctrl+Left Click to toggle the breakpoint. Double-click a line in
  the left margin to set a breakpoint. Single-click a line in the
  left margin to select a line without toggling the breakpoint.
  Use Ctrl+W to set Watches.

- Debugger window
  Click the Debug button to display the Debugger window. The Debugger 
  window has a menu and SpeedBar. The SpeedBar includes an X button 
  that stops execution and returns to the Design window. There's 
  also a Run to EndofMethod button and command in the Program menu.

  Choose Program|Origin to return to the last breakpoint.
  Choose View|Call Stack to open the Call Stack window, than right-click
  on a line to inspect its context in the Debug window. Choose 
  View|Source to select a form's methods to view.

- Stop sign cursor
  A stop sign cursor has been added to the form. When the Debugger is 
  at a breakpoint, any mouse click cause a beep.

- Tracer window 
  The Tracer window now includes a menu that lets you turn the Tracer
  on or off and select the built-in methods for tracing.


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

- Documentation:
  a) No printed documentation accompanies this field test. 
     Refer to online Help for information on Wiley features.
    
  b) Some material in Help has not yet been revised for Wiley--
     notably the help for the ObjectPAL IDE (see the previous
     section in this file for information on the IDE).

  c) Some jumps in Help do not function.
  
  d) Notes in red text surrounded by a border will not
     appear in the final product. Also, the cryptic pink text
     in the titles of some help topics will not appear
     in the final product.

- Interactive Tutors:
  a) When you click the Interactive Tutor SpeedBar button, or
     choose Help|Interactive Tutors, you can see the complete
     list of tutors, but only three tutors are implemented for
     this field test:

     BUILDING A DATABASE      WORKING WITH A TABLE                 
     "Creating A Table"       "Editing Records"                    
                              "Inserting And Deleting Records"    

    "Creating a Table" and "Inserting and Deleting Records" are
    only minimally tested. They are included so that you can see
    what we are planning.

  b) If you attempt to do something other than what the tutor
     instructs, your system might hang and need to be re-booted.

  c) Buttons at the end of each tutor will let you start a
     related tutor in the finished product. These buttons are
     not yet implemented.
     (The graphic at the beginning of each tutor will not be a
     pair of ducks in the final version of Wiley.)

- Experts are not available for this field test release.

- If you sort a table that has an autoincrement field, the
  sort renumbers the records, starting with the next unused
  number (for example, 1-5 becomes 6-10).

- SQL Links are not supplied in this field test release. If you
  have existing SQL Link drivers, Wiley lists these as available
  because IDAPI merged existing ODAPI.CFG settings when installed.
  The drivers you may see listed are not new drivers for Wiley.

- SETTINGS.TXT is included in your WILEY directory, but
  it is not yet updated for Wiley.

- The Advanced button on the Desktop Properties dialog box
  is not yet implemented.

- The sample table CONTACTS.DB is not included in the
  SAMPLE directory in Wiley.

- The new Data Model Designer:
  a) The hot keys are not implemented in this field test
     release.

  b) Do not load a saved data model that is not in the
     current working directory. There are problems with
     this in this field test release.

  c) Focus may be incorrectly shifted from the design window 
     to the Desktop or current document after particular actions
     are initiated from within the design window.

- Timestamp fields export as a blank string, or, in certain cases,
  as garbled characters from other fields.

- Opening the Fixed Length Export dialog box causes Wiley to crash.

- Using the system::importSpreadsheet method causes Wiley to crash.

- Calculated fields:
  a) The forward aggregator of an expression at the report level
     does not compute correctly (often returns 0).  Aggregators 
     of expressions placed in report headers and footers and page
     headers and footers all at once print blanks.  (Removing the 
     page level expression aggregators enables the expression 
     aggregator in the report footer to function properly).  


  b) Some calculated fields placed in a form do not always
     paint correctly. This sometimes shows up while navigating
     records that affect the value of the calculated field.

  c) An illegal calculated field such as

     SUM([number field] * [alpha field])

    does not cause a compile error in the Define Field dialog
    and prints nothing (blank) at runtime.

- Reports:
  a) Memos do not display/print properly in all circumstances.

  b) Some reports are not WYSIWYG between the previewer
     and the printer. This is especially true of reports
     containing long memos.

  c) Reports printed using style sheets sometimes
     print/display text slightly outside of design boundaries.

  d) Some reports start printing/displaying with page 0 and/or do not 
     increment properly.

  e) Opening a form as a report or a report as a form does not work
     properly, especially with aggregators of expressions.

- Install does not create the Local Configuration Utility icon.
  You must do this yourself (the following assumes that Wiley was
  installed in the Wiley directory):

  1. Activate the Wiley program group.
  2. Choose File|New|Program Item. 
  3. Enter the following:
     Description: Local Utility
     Command line: c:\wiley\pwlocal.exe
     Working Directory: c:\wiley
  4. Click OK, and the program item is created.

- When using Wiley as an OLE 2 container,
  a) If you have OLE objects in tables or forms, you may
     lose memory when you use these files. The memory loss
     occurs when the objects are loaded, so you may lose
     memory even if you don't activate any OLE objects.

  b) Some of the methods for the ObjectPAL OLE variable are not
     working: writeToClipboard and readFromClipboard do not work
     and return FALSE.

- When you use a table as an OLE 2 server, there are times 
  when Wiley should be hidden. In this field test version,
  Wiley is minimized instead of hidden.

- If you have a table with non-maintained indexes, and
  attempt to delete the primary key, your system will hang.

- Multi-Instance is not supported in this field test of Wiley. 
  You cannot run Wiley and Paradox 4.5 concurrently.

- Changing a timestamp field type to an Alpha that is too
  small will truncate the data with no warning. 

- Debug() statements do not automatically invoke the Debugger
  unless you first use a breakpoint to invoke the Debugger. 

- Live Answers:
a) Tables generated as the result of a Live Answer query do not
   support "quick" objects or default objects.

b) Tables generated as the result of a Live Answer query support
   filtered views, but do not support sorting by secondary index
   order.

- Workgroup Desktop:
a) Start OBEX.EXE before using Workgroup Desktop features or
   run ObjectPAL that uses WGPAL.LDL.

b) The cc:Mail and WPO transports are problematic. You should
   not use these two transports.

c) File|Send: People in the CC list do not currently receive
   the mail.

d) Address Book: Changing the Description field for an
   account in the Address composer dialog may cause a crash.

e) The Object Exchange cannot use address books created
   after OBEX starts running, although it can use new entries
   in existing address books. If you want to use aliases when
   addressing messages or publications, start the address book
   program first to make sure the book exists, then start OBEX,
   then start Paradox.

f) The Wiley OBEX uses a new address book; this field test
   version does not include the ability to import any old
   address books.

g) The Poll on Send feature (available from File|Send) is not
   yet implemented. You can poll manually using the Tools|
   OBEX Poll command.















