CICA 1995 September (Japanese)/CICA Shareware for Windows CD-ROM (Walnut Creek) (September 1995) (Japanese) (Disc 2).iso/disc2/access/accsvc.exe/ACCSVC/DISK1/READSRV.TXT

Text File | 1994-11-20 | 16.2 KB | 394 lines

_____________________________________________________

Microsoft Access Version 2.0 Service Pack Readme File
November 1994
_____________________________________________________


      (C) Copyright 1994 Microsoft Corporation


This document provides information about the Microsoft
Access version 2.0 Service Pack.  This release includes
the Microsoft Jet database engine version 2.5, the OLE
version 2.02 DLLs, and the Btrieve, Paradox, and xBASE
installable ISAM drivers.

You should install the files from this release if you
want the latest version of the Jet database engine and
the installable ISAM drivers or if you are currently
using or planning to use OLE custom controls.

Note  This new version of the Jet database engine will
work together seamlessly with the Jet database engine
version 2.0 (shipped with Microsoft Access version 2.0)
and with the Visual Basic version 3.0/Microsoft Access
version 2.0 Compatibility Layer.


________________________

How to Use This Document
________________________

To view the Readme file in Windows Notepad, maximize
the Notepad window.

To print the Readme file, open it in Windows Write,
Microsoft Word, or another word processor. Then select
the entire document and format the text in 10-point
Courier before printing it.


________

Contents
________

Installing the Microsoft Access Version 2.0 Service Pack
Adding OLE Custom Controls Created with the Microsoft OLE
 Custom Control Development Kit After Installing the Service
 Pack
Installing the Microsoft Access Developer's Toolkit Setup
 Wizard
Verifying the Jet Database Engine Version Number
Files Installed from the Microsoft Access Version 2.0
 Service Pack


________________________________________________________

Installing the Microsoft Access Version 2.0 Service Pack
________________________________________________________

This section describes how to install the Microsoft Access
version 2.0 Service Pack files from an online service or from
floppy disks.  If you're going to install the Service Pack on
a network file server or in a shared directory, first read
"Considerations for Network Installations" below.

The files that Setup installs are listed at the end of this
document.  For information about where Setup installs the files,
see the section titled "General Installation Notes."

Considerations for Network Installations
----------------------------------------
If you're setting up the Service Pack files on a network file
server, check the following before you begin:
* The network must be operational, and you must have create,
  write, and delete privileges for the network directories in
  which you want to install the files. For more information, see
  your network software documentation and the topic "Network
  Installations" in the Microsoft Access version 2.0 Readme Help
  (ACREADME.HLP).
* If any network users share the Windows operating system or other
  Microsoft applications, such as Microsoft Access and Microsoft
  Word (which share components), they must be logged off the
  network.  Users must not access the directories that contain
  shared components on the file server or shared volume -- for
  example, W:\WINDOWS and W:\MSAPPS -- while you are setting up
  the Service Pack. You must have create, write, and delete
  privileges in these directories.

Once you've installed the Microsoft Access version 2.0 Service
Pack files on the network from an online service or floppy disks,
each workstation user running Windows locally or from a shared
directory and running Microsoft Access locally or from a shared
directory must run Setup from the location on the network where
the Service Pack files are installed.

If users are installing Microsoft Access version 2.0 for the
first time, and if they want the Service Pack files, then they
must run two different Setup programs.  First, they run Setup
(either from floppy disks or from a network file server
or shared directory) for Microsoft Access, and then they run
Setup for the Service Pack.

Installing the Service Pack from an Online Service
--------------------------------------------------
To install the Service Pack from an online service onto a
stand-alone machine, network file server, or in a shared
directory
1. In the Windows File Manager, confirm that you have a
   directory named ACCSVC, which contains two subdirectories
   named DISK1 and DISK2.  If not, you may not have downloaded
   or decompressed the file ACCSVC.EXE correctly.
2. Choose Run from the File menu.
3. If you're installing on a network file server or in a shared
   directory, type <drive>:\ACCSVC\DISK1 SETUP /a
   Otherwise, type <drive>:\ACCSVC\DISK1 SETUP.
4. Follow the setup instructions on the screen.
   If you're installing on a network file server or in a shared
   directory, follow these guidelines:
   * Setup will install the files into the directory \ACC20SRV
     unless you specify a different directory.  If you specify a
     different directory, it can't have the same name as the
     directory where Access version 2.0 is installed on the file
     server.
   * The Service Pack doesn't include shared components;
     therefore, when Setup prompts you for information about
     them, do the following:

     In the Setup dialog box that asks if a directory other than
     MSAPPS should be used for shared components, choose OK.

     In the Setup dialog box titled Network Service Confirmation,
     choose Continue.

     In the Setup dialog box that prompts you to choose where the
     shared files will be installed, choose OK.

   * Each workstation user who needs the Service Pack files can
     now install them by running Setup from the ACC20SRV directory
     on the file server or from the directory where you installed
     the Service Pack.

For additional information about installing the Service Pack, see
the section titled "General Installation Notes," which appears
later in this document.

Installing the Service Pack from Floppy Disks
---------------------------------------------
Follow the procedure that applies to your situation.

To install the Service Pack from floppy disks onto a stand-alone
machine
1. Start Microsoft Windows, and quit any other applications.
2. Insert the disk labeled "Setup" in drive A.
3. In the Windows Program Manager, choose Run from the File
   menu.
4. Type a:setup in the Command Line box, and then choose OK.
5. Follow the setup instructions on the screen.

To install the Service Pack from floppy disks onto a network
file server or in a shared directory
1. Ask all users who are sharing Windows or Microsoft
   applications such as Microsoft Access and Microsoft
   Word to disconnect from the network file server or
   the shared directory.
2. Start Microsoft Windows, and quit any other applications.
3. Insert the disk labeled "Setup" in drive A.
4. In the Windows Program Manager, choose Run from the File menu.
5. Type a:setup /a in the Command Line box, and then choose OK.
   (The /a switch indicates an administrator's installation.)
6. Follow the setup instructions on the screen using the
   guidelines listed above in Step 4 under the section titled
   "Installing From an Online Service:"

General Installation Notes
--------------------------
When you install the Service Pack files on a network server,
you must run Setup /a from floppy disks, or from \ACCSVC\DISK1
if you downloaded the Service Pack from an online service. Do
not copy the files to a single directory on the hard disk and
then attempt to run Setup /a from there. If you do, the files
won't be properly configured on the network server, and users
won't be able to set up their workstations from the server using
Setup.

When Setup is run from floppy disks or from \ACCSVC\DISK1 on a
stand-alone machine, or when Setup is run from a network file
server or shared directory, it installs all files except
READSRV.TXT and JETVER.TXT into the WINDOWS\SYSTEM directory
when it doesn't find an existing version of the file in that
directory or when it finds an older version there.  It also
registers the information in OLE2.REG.  Setup installs
READSRV.TXT and JETVER.TXT into the directory C:\ACC20SRV
unless a different directory is specified during installation.


___________________________________________________________

Adding OLE Custom Controls created with the Microsoft OLE
Custom Control Development Kit After Installing the Service
Pack
___________________________________________________________

After installing the Service Pack, if you need to insert an
OLE custom control created with the Microsoft OLE Custom
Control Development Kit and the control was not previously
registered, you must follow the procedure below.  If
you don't follow this procedure, a serious error will
occur.

1. In Form Design view or Report Design view, choose Insert
   Object from the Edit menu.
2. Select the Insert Control button.  (If the OLE custom
   control you want to add is already in the Control Type
   list, just select the control from the list, and then
   click OK to insert it into the form.  Do not follow the
   steps below.)
3. Click the Add Control button.
4. Select the file for the control you want to add, and then
   choose OK.  Microsoft Access redisplays the Insert Object
   dialog box with your control added to the Control Type list.
5. Click the Cancel button.
6. Quit Microsoft Access, and then restart it.
7. Open the form or report in Design view again.
8. From the Edit menu, choose Insert Object.
9. Select the control you added previously, and then click OK.

Note  You do not need to follow the steps above if you're
inserting any of the custom controls that shipped in the
Microsoft Access Developer's Toolkit.


________________________________________________________________

Installing the Microsoft Access Developer's Toolkit Setup Wizard
________________________________________________________________


If you'll be distributing new Microsoft Access applications
using the Microsoft Access Developer's Toolkit, and if you want
to use the new Service Pack files for these applications, you
need to install an updated version of the Microsoft Access
Developer's Toolkit Setup Wizard. Use the procedure below
that applies to your situation.

IMPORTANT  You must have a Microsoft Access Developer's
Toolkit license before installing the updated version of
the Setup Wizard.  You receive a license when you buy a
retail Microsoft Access Developer's Toolkit package.

To install an updated version of the Microsoft Access
Developer's Toolkit Setup Wizard after downloading the
Service Pack from an online service
1. Quit all applications except Microsoft Windows.
2. In File Manager, select the directory ACCSRV, and then
   select the directory DISK2.
3. From the File menu, choose Run.
4. In the Command Line box, type:
   <drive>:decomp <drive>:SETUPWIZ.MD_ <Dstfilename>
   <drive> is the drive letter where you installed the Service
   Pack files. Dstfilename is the name, including the path, of
   the destination file.  (Use the path where the Microsoft
   Access Developer's Toolkit files are installed --
   usually \ACCESS\ADT.)  An example of the destination
   filename is c:\ACCESS\ADT\SETUPWIZ.MDB.
5. When the warning message appears that tells you the file
   already exists and asks if you want to append the file,
   choose No.
6. When the warning message appears that asks if you want to
   overwrite the existing file, choose Yes.

To install an updated version of the Microsoft Access
Developer's Toolkit Setup Wizard from the Service Pack
floppy disks
1. Start Microsoft Windows, and quit any other applications.
2. Insert the second disk from the pack into drive A.
3. In the Windows Program Manager, choose Run from the File
   menu.
4. In the Command Line box, type:
   a:decomp a:\SETUPWIZ.MD_ <Dstfilename>
   Dstfilename is the name, including the path, of the
   destination file.  (Use the path where the Microsoft
   Access Developer's Toolkit files are installed --
   usually \ACCESS\ADT.)  An example of the destination
   filename is c:\ACCESS\ADT\SETUPWIZ.MDB.
5. At the warning message that tells you the file already
   exists and asks if you want to append the file, choose No.
6. At the warning message that asks if you want to overwrite
   the existing file, choose Yes.

Note  If you've already distributed Microsoft Access run-time
applications using the Microsoft Access Developer's Toolkit,
you may send copies of the Service Pack to your customers to
upgrade to the Jet database engine version 2.5 and OLE
version 2.02. You must use the Service Pack setup unchanged.


________________________________________________

Verifying the Jet Database Engine Version Number
________________________________________________

After installing the Microsoft Access version 2.0 Service Pack,
the Jet .DLL files retain the same file names (for example,
MSAJT200.DLL).  If you want to verify what version of Jet you
have and that you are the only one using a particular Microsoft
Access database, choose About Microsoft Access from the Help
menu in Microsoft Access, and then choose System Info.

To verify the Jet database engine version number from the About
Microsoft Access dialog box in Microsoft Access
1. From the Help menu, choose About Microsoft Access.
2. Choose the System Info button.
3. In the Choose a Category box, click the arrow, and then choose
   System DLL's from the list.
4. Scroll to MSAJT200.DLL in the list.
   The version number is to the right of the file name.

Note  You can use this procedure to check the version numbers of
the OLE and ISAM DLLs, too.  However, the version number for the
file OLE2CONV.DLL remains the same (2.01) even after you install
the latest version from the Service Pack.

If you are a network administrator, you can automatically verify
that everyone using a particular Microsoft Access database on a
network file server or in a shared directory has the Jet database
engine version 2.5 on their workstation.  You can do this by
calling the sample code provided in the JETVER.TXT file in the
Service Pack from a new or existing AutoExec macro.

Once you've followed the procedure below, users who don't have
the Jet database engine version 2.5 installed on their work-
station receive a message to that effect and are prevented from
opening the database.

To verify the Jet database engine version number using the
code provided in JETVER.TXT
1. Create a new module in the Microsoft Access database where
   you want to use the code.
2. From the File menu in the Module window, choose Load Text.
3. Type JETVER.TXT, or choose it from the appropriate directory.
4. Choose the Replace button.
5. Save the module with the name Init.
6. Open the existing AutoExec macro or create a new one.
7. Add a RunCode action as the first action in the macro.
8. In the arguments section at the bottom of the window, type
   the function name Init().
9. Save the macro.  (If this is a new macro, save it with the
   name AutoExec.)

Note  You can modify the code module to fit your needs.  For
example, you may want to change the message text to better suit
your user environment.


__________________________________________________________________

Files Installed from the Microsoft Access Version 2.0 Service Pack
__________________________________________________________________

This section lists the files installed by the Microsoft Access
version 2.0 Service Pack Setup.

Besides being available from this release, the following files
are also included in the ODBC Desktop Driver Pack version 2.0 or
an application based on the ODBC Desktop Driver Pack version 2.0.


Files
------------
MSAJT200.DLL
MSAJU200.DLL
MSJETERR.DLL
MSJETINT.DLL
JETVER.TXT
BTRV200.DLL
PDX200.DLL
XBS200.DLL
COMPOBJ.DLL
OLE2.DLL
OLE2CONV.DLL
OLE2DISP.DLL
OLE2NLS.DLL
OLE2PROX.DLL
STORAGE.DLL
TYPELIB.DLL
STDOLE.TLB
OLE2.REG
CTL3D.DLL
READSRV.TXT