The following list identifies problems that may occur when using Microsoft
Access.  A detailed description of each problem and the suggested work around
is also provided.

1.      Incorrect Windows For Workgroups driver can cause file truncation
        (correct driver included with Microsoft Access).
2.      Incorrect LAN Manager driver can cause file truncation (correct driver
        included with Microsoft Access).
3.      Microsoft Access SETUP may have problems with DOS APPEND statement in
        autoexec.bat
4.      ATI Ultra video driver not compatible with Microsoft Access.
5.      Microsoft Access SETUP may leave temporary directory and files on hard
        disk.
6.      Problem importing .DBF files where record length exceeds dBASE maximum.
7.      Microsoft Access cannot use Btrieve data with indexes across column
        boundaries.
8.      Fixed Width import does not correctly translate extended characters.
9.      Cannot hide modal/popup forms with the OpenForm action.
10.     Form dynaset references are problematic when using form variables.
11.     Problem using Running Sum property with control that evaluates to
        #ERROR.
12.     Beta versions of ODBC drivers will not work with Microsoft Access.

In addition to these problems, we are in the process of investigating reports
of incompatibilities and problems using Microsoft Access with Stacker 3.0 and
the Btrieve NLM.  We will post additional information as soon as it is
available.


1.      Incorrect Windows For Workgroups driver can cause file truncation
        (correct driver included with Microsoft Access).

NOTE: This problem was discovered  before Microsoft Access was released and
all copies of Microsoft Access include the updated Windows for Workgroups
driver and installation instructions.

DESCRIPTION:  If you have an early version of the Windows for Workgroups
WFWNET.DRV file (11-02-92 or earlier), using the Network button in Access
dialog boxes to connect to password-protected servers may cause any database
files that you open on that server to become truncated.

RESOLUTION: Update the WFWNET.DRV driver file using the driver update program
included with Microsoft Access.  Complete instructions are contained in the
flier included in your copy of Microsoft Access.


2.      Incorrect LAN Manager driver can cause file truncation (correct driver
        included with Microsoft Access).

NOTE: This problem was discovered before Microsoft Access was released and all
copies of Microsoft Access include the updated LAN Manager driver and
installation instructions.

DESCRIPTION:  Using Microsoft Access on a Microsoft LAN Manager workstation
(prior to version 2.2) can cause files to become truncated.  Products that may
be affected include: Microsoft LAN Manager prior to version 2.2; DEC Pathworks
for DOS version 4.1; NCR StarGroup LAN Manager version 3.6; Olivetti Olinet
LAN Manager version 2.1; Ungermann-Bass LAN Manager version 2.1.

Database truncation is most likely to occur when a user workstation operates
faster than the file server on which the database file is stored. (Note that
the CPU speed alone does not determine the operation speed of the server.
Heavy network traffic can make the server operate more slowly than a user
workstation(s).)

RESOLUTION: If you have LAN Manager 2.1 or 2.1a, install the LAN Manager
Hotfix included with Microsoft Access appropriate to your version of LAN
Manager.  If you have LAN Manager 2.0, include the appropriate line in your
LANMAN.INI file for LAN Manager versions prior to 2.1.  Refer to the
instructions included in the README.TXT file in your Microsoft Access package
for complete details.


3.      Microsoft Access SETUP may have problems with DOS APPEND statement in
        autoexec.bat

DESCRIPTION: If you have an APPEND statement in your AUTOEXEC.BAT file and
that APPEND statement defines a path where other README.TXT files exist,
Microsoft Access SETUP can fail when installing the README.TXT file.

RESOLUTION: Remove or remark out the APPEND statement in your AUTOEXEC.BAT
file and reboot your computer before trying to setup Microsoft Access.


4.      ATI Ultra video driver not compatible with Microsoft Access

DESCRIPTION:  Using ATI-supplied drivers included with the ATI Ultra video
card can cause any of the following problems in Microsoft Access: 1) General
Protection Fault on disabled cascading menus (most common case is Layout menu
with Align command disabled in form or report design); 2) disabled buttons not
visible; and 3) text alignment problems.

RESOLUTION: The suggested work around for these problems is to use the 8514
video drivers included with Windows 3.1 and not the video drivers supplied
with the ATI Ultra video card.  NOTE: Microsoft is working with ATI on this
problem.  We will post more information on this forum as it becomes available.


5.      Microsoft Access SETUP may leave temporary directory and files on your
        hard disk

DESCRIPTION:  If you request SETUP to install SHARE and then choose the option
to reboot your machine at the end of the installation process, SETUP will not
properly clean up temporary files on your hard disk.  This leftover directory
will have the name MS-SETUP.T and will contain data files totaling
approximately 600K.  Besides taking up hard disk space, these files will have
no affect on Microsoft Access or any other applications.

RESOLUTION: Do not choose to reboot your machine at the end of the installation
process or simply delete the files and directory after the reboot process.


6.      Problem importing .DBF files where record length exceeds dBASE Maximum

DESCRIPTION: CodeBase ++ v1.07 allows you to create .DBF files where the record
length exceeds the dBASE IV maximum.  Microsoft Access may hang when trying to
import these type of .DBF files.

RESOLUTION:  Export the CodeBase++ .DBF file to delimited text, then import the
ASCII file into Microsoft Access.


7.      Microsoft Access cannot use Btrieve data with indexes across column
        boundaries

DESCRIPTION: Microsoft Access will display the error message:  "File is corrupt
or isn't an Access file" when attempting to attach or import a Btrieve file
which has an index defined across a column boundary.  Access does not support
Btrieve indexes which have keys defined on a partial column or across column
boundaries.  Indexes which have a segment of the key which is defined to cross
a column boundary are not supported by the Xtrieve data dictionary format.
Xtrieve may ignore these indexes and import the file correctly but Microsoft
Access does not.

RESOLUTION:  You must remove the indexes or recreate them so that they align
on column boundaries.


8.      Fixed Width import does not correctly translate extended characters

DESCRIPTION: When importing a Fixed Width ASCII file, Microsoft Access does not
properly translate  extended characters from OEM  to ANSI representation.  The
first 4K of data is imported and translated correctly, but all data after the
initial 4K will not translate correctly.

RESOLUTION: Convert the ASCII file from OEM to ANSI using another Windows
application, such as Windows Write.  Using Windows Write, simply open the file,
responding 'Yes' to the convert alert, then save the file.


9.      Cannot hide modal/popup forms with the OpenForm action

DESCRIPTION: Using the OpenForm action to hide a modal/popup form may cause a
General Protection Fault.

RESOLUTION: Hide a modal/popup form by using the SetValue action to set the
forms Visible property to False.


10.   Form dynaset references are problematic when using form variables

DESCRIPTION: If you reference a form dynaset with variables, you may receive
a General Protection Fault.

RESOLUTION: Always refer to a form dynaset with explicit references through
the form.  The first code fragment below shows how to references a form dynaset
safely and the second code fragments shows what will most likely cause the
problem.

A)      SAFE:
        forms!testform.dynaset!col1="foo"

B)      MAY CAUSE PROBLEMS:
        dim f as form
        set f = form!testform
        f.dynaset!col1 = "foo"


11.     Problem using Running Sum property with control that evaluates to
        #ERROR

DESCRIPTION: If a report contains a control where the Running Sum property is
set to 'Over Group' or 'Over All' and the control evaluates to #ERROR,
Microsoft Access will cause a General Protection Fault.

RESOLUTION: Correct the expression in the control source property so that it
evaluates correctly.


12.     Beta versions of ODBC drivers will not work with Microsoft Access

DESCRIPTION:  When using Beta versions of the ODBC drivers, Microsoft Access
may experience General Protection Faults in ODBC.DLL.  The problem is that when
Microsoft Access initiates an ODBC connection, ODBC does not properly check the
version of the ODBC driver.

RESOLUTION: Rename or delete the beta version of ODBC.DLL and run the ODBC
setup program from the setup disks that come with Microsoft Access.  This will
install a current ODBC.DLL file.
                              ***********
