Liren Large Software Subsidy 6

home *** CD-ROM | disk | FTP | other *** search

/ Liren Large Software Subsidy 6 / 06.iso / a / a560 / 8.ddi / README_.TX$ / README_.bin

Wrap

Text File | 1993-01-03 | 28.9 KB | 765 lines

---------------------------------------- Microsoft Access Version 1.0 README File December 22, 1992 ---------------------------------------- (C) Copyright Microsoft Corporation, 1992 This document provides complementary or late-breaking information as a supplement to the standard Microsoft Access documentation. ------------------------ How to Use This Document ------------------------ To view README on screen in Windows Notepad, maximize the Notepad window. To print README, 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. -------- Contents -------- Microsoft Access Q&A Using Microsoft Access with Microsoft LAN Manager Using Microsoft Access with Microsoft Windows for Workgroups Setting Up Microsoft Access with a Microsoft License Pak Setting Up Microsoft ODBC (Open Database Connectivity) Configuring Microsoft SQL Server for Use with ODBC Setting Up Microsoft ODBC for Use with Microsoft SQL Server on a Novell Network Using Microsoft Access to Read and Write Data to a Novell Btrieve File Importing and Exporting Data from FoxPro Enhancing Performance Installing International Versions of Cue Cards Analyzing Database Structure Using Sample Applications Solving Problems Printing Forms and Reports Using Microsoft Access as a DDE Server Microsoft Access Files Important: The errata and omissions in Microsoft Access documentation are contained in ERRATA.TXT in the Microsoft Access program directory. -------------------- Microsoft Access Q&A -------------------- The Microsoft Access Setup program installs the Microsoft Access Q&A file and creates a Notepad icon in the Microsoft Access program group. This file contains answers to the questions most frequently asked by beta sites about Microsoft Access. To view the file, double-click the icon. ------------------------------------------------- Using Microsoft Access with Microsoft LAN Manager ------------------------------------------------- The following problem may occur when using products based on Microsoft LAN Manager versions prior to 2.2 on your MS-DOS or PC-DOS workstation. Using Microsoft Access on an MS-DOS or PC-DOS workstation running a product based on versions of Microsoft LAN Manager prior to version 2.2 can irreparably corrupt a database file. Database corruption is most likely to occur when a user workstation operates faster than the file server storing the database file. (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).) Products that may be affected include: DEC Pathworks for DOS version 4.1 Microsoft LAN Manager prior to version 2.2 NCR StarGroup LAN Manager version 3.6 Olivetti Olinet LAN Manager version 2.1 Ungermann-Bass LAN Manager version 2.1 See your network administrator to find out if the information in this section applies to your network software. To prevent data corruption when using the enhanced version of Microsoft LAN Manager version 2.1 or 2.1a, your network administrator should install the Hotfix that is included on the ODBC disk. To determine your version of Microsoft LAN Manager: 1 Type net ver at the MS-DOS prompt to determine which version of LAN Manager is installed on the user workstation. You will see information such as the following: C:\>NET VER Microsoft LAN Manager Version 2.1.0 DOS Enhanced Workstation Created at 11-15-91 07:27am Proceed to the procedure, "To install the Hotfix on each user workstation," only if the command reports you are using Microsoft LAN Manager version 2.1 or 2.1a. If the command does not report which version of Microsoft LAN Manager you are using, you are using a version earlier than 2.1. You need to upgrade the workstation to Microsoft LAN Manager version 2.2 or follow the procedure, "To adapt a workstation using a version of Microsoft LAN Manager prior to 2.1," at the end of this section. Important: If you are using network software based on Microsoft LAN Manager and aren't sure which version of Microsoft LAN Manager it corresponds to, do not install the Hotfix. Instead, follow the procedure, "To adapt a workstation using a version of Microsoft LAN Manager prior to 2.1." You can install the Hotfix later if it's determined you need it. To install the Hotfix on each user workstation: 1 Type ver at the MS-DOS prompt to determine which version of MS-DOS is installed on the user workstation. 2 Insert the ODBC disk in drive A. 3 Copy the appropriate NETWKSTA file on the ODBC disk to the LAN Manager NETPROG directory and rename the file as NETWKSTA.EXE. For example, if LAN Manager is currently installed in the LANMAN.DOS directory on the C: drive, and you are using MS-DOS 5.0, type: copy a:netwksta.500 c:\lanman.dos\netprog\netwksta.exe 4 Reboot the user workstation. To adapt a workstation using a version of Microsoft LAN Manager earlier than 2.1: To prevent database corruption when using versions of Microsoft LAN Manager earlier than version 2.1, turn write-behind off by adding or modifying the following line in the [workstation] section of your LANMAN.INI file: [workstation] wrkheuristics=X0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (NOTE: The Xs are placeholders for values in the range of 0-2. In all, there should be 33 values in this entry, and the second value must be 0 (zero). See your Microsoft LAN Manager Administrator's Reference for details.) Important: If this line already exists in your LANMAN.INI file, change only the second value to 0 (zero). Note that adding this line may slightly decrease the performance of your system. You can also resolve this problem by upgrading to LAN Manager version 2.2 or later. For details, please contact your network vendor or Microsoft Product Support at the numbers listed in your Microsoft Access User's Guide or in Microsoft Access Help. (Select Contents from the Help menu, and then click Product Support.) ------------------------------------------------------------ Using Microsoft Access with Microsoft Windows for Workgroups ------------------------------------------------------------ Important: Before You Use Microsoft Access with Microsoft Windows for Workgroups ---------------------------------------------------------- While running Microsoft Windows for Workgroups, if you use the Network button in Microsoft Access dialog boxes to connect to a password-protected server, you may lose data. To avoid damaging your database, you must install the updated Microsoft Windows for Workgroups Driver included with Microsoft Access. Until you have installed this driver, do not use the Network button in Microsoft Access dialog boxes to make network connections. Note: If you are considering installing Windows for Workgroups at a later date, install the updated driver now. To install the updated Windows for Workgroups Driver: 1 Exit Microsoft Windows or Windows For Workgroups. This driver cannot be installed while you are running Microsoft Windows. 2 Insert the ODBC disk in drive A. 3 Type a:wfwdrv * If Windows is installed on your PC, but is not in your PATH statement in AUTOEXEC.BAT, enter the path where Windows is installed. For example, type: a:wfwdrv c:\windows. * If Windows is installed on the network, specify the system directory where USER.EXE is found. For example, to install the driver into the q:\system directory type: a:wfwdrv q:\system 4 Type win to restart Windows. If you have any questions about this driver, please contact Microsoft Product Support Services for Windows for Workgroups. Using Microsoft SQL Server Data Installed on a Novell NetWare LAN or a Banyan Network -------------------------------------------------- If you use Microsoft Access on a workstation running under Microsoft Windows for Workgroups and want to access Microsoft SQL Server data installed on a Novell NetWare LAN or a Banyan network, you must use the SQL Server Network Integration Kit (NIK). For details, please contact Microsoft Product Support at one of the numbers listed in your Microsoft Access User's Guide or in Microsoft Access Help. (Select Contents from the Help menu, and then click Product Support.) -------------------------------------------------------- Setting Up Microsoft Access with a Microsoft License Pak -------------------------------------------------------- The first time you install Microsoft Access using the Microsoft License Pak, Setup stores the company name but not the user name. Setup customizes the user name for each installation. To install Microsoft Access using the Microsoft License Pak 1 Choose Run from the Windows Program Manager File menu. 2 Change to the directory in which the Microsoft Access program files are stored. 3 In the Command Line box type: setup /l ------------------------------------------------------ Setting Up Microsoft ODBC (Open Database Connectivity) ------------------------------------------------------ When you install Microsoft ODBC, install it in its own directory, not in the directory where you installed Microsoft Access. -------------------------------------------------- Configuring Microsoft SQL Server for Use with ODBC -------------------------------------------------- To configure Microsoft SQL Server properly for use with ODBC (Open Database Connectivity), you must run the SQL Script file INSTCAT.SQL to set up the stored procedures that provide catalog information used by ODBC. (Note: If you are using Sybase SQL Server version 4.8 or higher, you will need a special version of INSTCAT.SQL. For details, call Microsoft Product Support at one of the numbers listed in your Microsoft Access User's Guide or in Microsoft Access Help-- select Contents from the Help menu, and then click Product Support.) If INSTCAT.SQL hasn't been properly installed, the following error message is displayed while you're attaching an SQL table in Microsoft Access: [Microsoft][ODBC SQL Server Driver] The ODBC catalog stored procedures installed on your server <servername> are version xx.xxxx; version xx.xx.xxxx is required to ensure proper operation. Please contact your system administrator. To install the catalog stored procedures, use the SQL Server ISQL (Interactive SQL) tool. You can run the ISQL tool from the MS-DOS or OS/2 command line. (NOTE: Don't use the SAF utility provided with Microsoft SQL Server. Microsoft SAF for MS-DOS and OS/2 is limited to 511 lines of code in an SQL script.) The syntax to install INSTCAT.SQL using ISQL is: isql /U <sa loginname> /n /P <password> /S <SQL servername> /i <drive:\path\INSTCAT.SQL> /o <drive:\path\outputfilename> (NOTE: Enter the preceding two lines as one line at the command prompt, and don't include the angle brackets < >.) /U Login name for the system administrator. /n Eliminates line numbering and prompting for user input. /P Password (case sensitive) used for the system administrator. /S Name of the driver to set up. /i Provides the drive and fully qualified path for INSTCAT.SQL. /o Provides ISQL with an output file destination for results, including errors. Example: isql /U sa /n /P skier /S DUMMY_SERVER /i D:\SQL\INSTCAT.SQL /o D:\SQL\OUTPUT.TXT ----------------------------------------------------------- Setting Up Microsoft ODBC for Use with Microsoft SQL Server on a Novell Network ----------------------------------------------------------- If you are installing ODBC on a Novell or Banyan network, you will receive a warning message from the ODBC Setup program stating that the network host you specified was not found on the network. Simply confirm that you want to use the network host that you specified and accept the default settings that ODBC Setup supplies. If you use the Microsoft SQL Server Network Integration Kit (NIK), you'll need to enter the following information in the ODBC SQL Server Setup dialog: - Network Address: The name of the database server as specified in the server parameter of the Network Manager running on the server. - Network Library: The name of the NIK network library. For example, "dbmsspx3" for the Novell NIK and "dbmsvin3" for the Banyan NIK. Also note that when using the NIK, you will see DSQUERY as a choice for installing a data source for SQL Server. DSQUERY is a reserved name which sets the default network library. You should not install it as an ODBC data source. -------------------------------------------------- Using Microsoft Access to Read and Write Data to a Novell Btrieve File -------------------------------------------------- To use Microsoft Access to read and write data to a Novell Btrieve file, you must have a copy of the stand-alone Btrieve for Windows WBTRCALL.DLL file (about 52K in size). This file must be in your \windows\system directory. You may already have a copy of this file on your hard drive. To find it, at the root directory type dir wbtrcall.dll /s Copy this file to your \windows\system directory. Important: If you already have a copy of WBTRCALL.DLL in your \windows\system directory, contact your system administrator before copying over it. This file may be used by other programs on your computer. If you don't have a copy of this file, you can purchase Btrieve for Windows from Novell Inc. by calling 800-453-1267 or by contacting your local software dealer. ---------------------------------------- Importing and Exporting Data from FoxPro ---------------------------------------- The procedures for importing data from and exporting data to FoxPro databases are similar to those for dBASE (except, as noted here, the dBASE procedures apply to any file created by FoxPro version 2.0 and earlier). These procedures are covered in Chapter 4, "Importing, Exporting, and Attaching," in the Microsoft Access User's Guide. To import data from a FoxPro file, follow the procedure "To import or attach a dBASE file" on page 64. In step 3, select FoxPro 2.0 in the Data Source list box. (If you're using the FoxPro database in a multiuser environment, you must have exclusive access to the file that you want to import. If other users have the file open, you won't be able to import it.) When you import data from a FoxPro file, Microsoft Access translates FoxPro data types into the corresponding Microsoft Access data types. For a list of conversions, see the table, "dBASE to Microsoft Access Data Type Conversions" on page 65. (Note: You can't attach a FoxPro file or import index files associated with the .DBF file.) To export data to a FoxPro database, follow the procedure "To export a Microsoft Access table to a spreadsheet or database file" on page 85. --------------------- Enhancing Performance --------------------- To enhance the performance of large tables and of complex queries or reports, you can increase the amount of buffer space used by Microsoft Access. By default, Microsoft Access uses 512K of memory for its internal buffers. You can increase the buffer space up to 4096K by adding an entry for MaxBufferSize under the [ISAM] section of the MSACCESS.INI file--for example, enter "MaxBufferSize = 4096" to increase the buffer size to 4096K. (Setup stores the MSACCESS.INI file in your Windows directory.) Your machine must have enough physical memory to support the increased buffer size. For more information on optimizing performance, search Microsoft Access Help for "performance." ---------------------------------------------- Installing International Versions of Cue Cards ---------------------------------------------- You will not be able to use Cue Cards if you install it in a directory whose name contains a ligature, such as the characters ▀ and µ. To resolve this problem, delete all the Microsoft Access files and remove the directory. Then rerun Microsoft Access Setup. ---------------------------- Analyzing Database Structure ---------------------------- When you develop a new database or modify an existing one, you'll probably want detailed information about its structure. Microsoft Product Support Services provides an informal diagnostic tool for this purpose called the Database Analyzer. Using this tool, you can display or print tables listing the structural features of many of the objects in a database. For information on installing and using the Database Analyzer, read question 23 in PSSKB.TXT found in your Microsoft Access program directory. ------------------------- Using Sample Applications ------------------------- In addition to the Northwind Traders database (NWIND.MDB), which is used in examples throughout the Microsoft Access documentation, you can install two sample applications: Personal Information Manager (PIM.MDB) and Order Entry (ORDENTRY.MDB). These are just two examples of the types of applications you can create with Microsoft Access. You can use them as a learning tool for creating your own applications, and perhaps in your daily work and business as well. If you chose the Complete Installation option when you installed Microsoft Access, the Setup program installed the sample application files. If you made a different choice or if you have removed the files, you can install them by running Setup again, choosing Custom Installation, and selecting Sample files. Setup installs the files in the program directory. General information and instructions on using each application are available online for the Personal Information Manager and Order Entry applications. To use this information, start Microsoft Access and open the database file for the application. Then press F1 or choose Contents from the Help menu. (Note: The Personal Information Manager and Order Entry applications are designed to be run on a VGA monitor only.) ------------------------------------------- Solving Problems Printing Forms and Reports ------------------------------------------- Microsoft Access forms or reports, because of a driver problem, may not print correctly on an HP LaserJet IIISi printer using non-TrueType fonts. For best results, use TrueType fonts with this printer. -------------------------------------- Using Microsoft Access as a DDE Server -------------------------------------- Microsoft Access supports dynamic data exchange (DDE) as both a destination (client) and a source (server). This section describes the five topics that Microsoft Access supports as a DDE server and the items that are valid for each topic. The five topics are "System", <database>, <table name>, <query name>, and "SQL <expr>". For information on using Microsoft Access as a DDE client, see Chapter 13, "Using Pictures, Graphs, and Other Objects," in the Microsoft Access User's Guide. "System" Topic -------------- "System" is a standard topic for all Windows applications. It returns information about the topics Microsoft Access supports. The following table lists the valid items for the "System" topic. Item Returns ---------------------------------------------------------- SysItems A list of items supported by the topic "System" Format A list of the formats Microsoft Access can copy onto the Clipboard Status "Busy" or "Ready" Topics A list of all open databases <macro name> Runs a macro in the current database NOTE: To send the name of a macro to the current Microsoft Access database, use the DDEExecute statement. In order to run, the macro must be contained in the current database. <database> Topic ---------------- <database> is the file name of an existing database. This topic can be a fully qualified path to the file and may include the .MDB extension. You cannot use DDE to query the SYSTEM.MDA. After you initiate a DDE link with a database, you can request a listing of the objects in that database. Item Returns ---------------------------------------------------------- TableList A list of tables QueryList A list of queries MacroList A list of macros ReportList A list of reports FormList A list of forms ModuleList A list of modules <macro name> Runs a macro in the currently open database <table name> and <query name> Topics ------------------------------------ The <table name> and <query name> topics support the same items. When requesting the contents of a table or the results of a query, you must specify the database the object is in, followed by a semicolon, the keyword TABLE (or QUERY), and then the name of an existing table or query. The syntax for these topics is: <database>;TABLE <table name> <database>;QUERY <query name> To request the contents of the Categories table in the sample database, NWIND.MDB, you can type just the name of the database or its full path: NWIND;TABLE Categories or c:\Access\NWIND.MDB;QUERY Category List (Note: Do not enclose table or query names in brackets [ or ].) The following table lists the items that are valid with the <table name> and <query name> topics. Item Returns ---------------------------------------------------------- All All the data in the table, including field names. Data All rows of data without field names. FieldNames A list of field names. NextRow The next row in the table or query. When you first initiate a channel, NextRow returns the first row. If the current row is the last record and you execute NextRow, the request fails. PrevRow The previous row in the table or query. If PrevRow is the first request over a new channel, the last row of the table or query is returned. If the current row is the first record, the request for PrevRow fails. FirstRow The data in the first row of the table or query. LastRow The data in the last row of the table or query. FieldCount The number of the fields in the table or query. "SQL <expr>" ------------------ The "SQL <expr>" topic returns the results of the specified SQL expression. The syntax for this topic is: <database>;SQL <expr> For example, to select all fields from the Employees table in the Northwind database, enter: NWIND;SQL Select * from Employees; To select only the values in the First Name field in the Employees table, enter: c:\ACCESS\NWIND.MDB;SQL Select [First Name] from Employees; Note: End each SQL statement with a semicolon (;). The "SQL <expr>" topic supports the same items as the <Table Name> and <query name> topics. ---------------------- Microsoft Access Files ---------------------- File Name Destination Description 1.wmf N/A Billboard displayed during setup. VGA and better resolution. 1e.wmf N/A Billboard displayed during setup. EGA resolution. 2.wmf N/A Billboard displayed during setup. VGA and better resolution. 2e.wmf N/A Billboard displayed during setup. EGA resolution. 3.wmf N/A Billboard displayed during setup. VGA and better resolution. 3e.wmf N/A Billboard displayed during setup. EGA resolution. 4.wmf N/A Billboard displayed during setup. VGA and better resolution. 4e.wmf N/A Billboard displayed during setup. EGA resolution. 5.wmf N/A Billboard displayed during setup. VGA and better resolution. 5e.wmf N/A Billboard displayed during setup. EGA resolution. 6.wmf N/A Billboard displayed during setup. VGA and better resolution. 6e.wmf N/A Billboard displayed during setup. EGA resolution. 7.wmf N/A Billboard displayed during setup. VGA and better resolution. 7e.wmf N/A Billboard displayed during setup. EGA resolution. 8.wmf N/A Billboard displayed during setup. VGA and better resolution. 8e.wmf N/A Billboard displayed during setup. EGA resolution. btrvisam.dl$ <Program> Btrieve ISAM DLL. cbtlib4.dl$ <Program> Cue Cards DLL commdlg.dl$ <Windows\System> Common dialog boxes. This is a file shipped with Windows 3.1. commdlg.dl_ N/A Uncompressed version of common dialog boxes used by setup program. ctl3d.dl$ <Windows> 3D-look DLL. cuecard.ex$ <Program> Cue Cards executable. cuecards.dl$ <Program> Cue Cards communication DLL. cuecards.le$ <Program> Cue Cards lesson file. dbsisam.dl$ <Program> dBASE ISAM DLL. ddeml.dl$ <Windows\System> DDE support DLL. detcmd.dl_ <Program> DLL used by Setup. errata.tx$ <Program> Microsoft Access documentation errata file. Contains late changes to documentation. graph.ex$ \windows\msapps\ msgraph Microsoft Graph executable. msabc100.dl$ <Program> Microsoft Access Basic code DLL. msacces2.hl$ <Program> Part 2 of the Microsoft Access Help file. msaccess.ex$ <Program> Microsoft Access executable. msaccess.hl$ <Program> Part 1 of the Microsoft Access Help file. msaccess.in$ <Windows> Microsoft Access initialization file. msaccess.re$ N/A Input file for additions setup makes to the OLE registration database. msaes100.dl$ <Program> Microsoft Access expression service DLL. msafin.dl$ <Program> Additional financial functions DLL. msain100.dl$ <Program> International resources for Microsoft Access. msajt100.dl$ <Program> Microsoft Access JET engine. msaju100.dl$ <Program> Microsoft Access JET engine utilities. msgraph.hl$ \windows\msapps \msgraph Microsoft Graph Help file. newcust.db$ <Program> Sample dBASE file used in "Getting Started" nwind.md$ <Program> Northwind Traders sample database. olecli.dl$ <Windows\System> OLE Client support DLL. olesvr.dl$ <Windows\System> OLE Server support DLL. ordentry.hl$ <Program> Order Entry sample application help file. ordentry.md$ <Program> Order Entry sample application database. ordentry.tx$ <Program> Order Entry sample application readme. pdxisam.dl$ <Program> Paradox 3.5 ISAM DLL. pim.hl$ <Program> Personal Information Manager help file. pim.md$ <Program> Personal Information Manager database. psskb.tx$ <Program> Microsoft Access Questions and Answers text file. Top Q&A from early users. readme_.tx$ <Program> Microsoft Access readme file. Contains issues you should be aware of. (This file.) regedit.ex$ <Windows> Windows 3.1 registration database editor. setup.exe N/A Setup executable. setup.ini <Program> Setup initialization file. share.ex$ <Windows> MS-DOS 5.0 file locking utility. (Not installed if already present.) shell.dl$ <Windows\System> Windows 3.1 utility DLL. smallb.fo$ <Windows\System> Required font for Microsoft Access. smalle.fo$ <Windows\System> Required font for Microsoft Access. smallf.fo$ <Windows\System> Required font for Microsoft Access. stfsetup.ex_ <Program> Microsoft Access 2nd-level setup executable. Also used by Change Workgroup. stfsetup.in_ N/A Microsoft Access 2nd-level setup initialization file. system.md$ <Program> Base system database. You must use setup to install this file as important customization is done during setup. utility.md$ <Program> Microsoft Access utility database. ver.dl$ <Windows\System> Windows 3.1 version checking DLL. ver.dl_ N/A Uncompressed version of Windows 3.1 version checking DLL used during setup. winhelp.ex$ <Windows> Windows 3.1 help program. winhelp.hl$ <Windows> Windows 3.1 help program help file. wizard.md$ <Program> Microsoft Access Wizards. workgrp.in_ <Program> Microsoft Access workgroup initialization file used during setup. Renamed to stfsetup.inf.