{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "1 WMF", "size": 4470, "date": "1993-05-26", "time": "12:00" }, { "name": "1E WMF", "size": 4022, "date": "1993-05-26", "time": "12:00" }, { "name": "BTRV110 DL$", "size": 59436, "date": "1993-05-26", "time": "12:00" }, { "name": "COMMDLG DL$", "size": 46406, "date": "1993-04-22", "time": "8:25" }, { "name": "COMMDLG DL_", "size": 46406, "date": "1993-05-26", "time": "12:00" }, { "name": "CTL3D DL$", "size": 8410, "date": "1993-04-22", "time": "8:25" }, { "name": "DDEML DL$", "size": 20305, "date": "1993-04-22", "time": "8:25" }, { "name": "DECOMP EXE", "size": 40695, "date": "1993-05-26", "time": "12:00" }, { "name": "DETCMD DL_", "size": 24128, "date": "1993-05-26", "time": "12:00" }, { "name": "MSACCESS IN$", "size": 582, "date": "1993-05-26", "time": "12:00" }, { "name": "MSACCESS RE$", "size": 552, "date": "1993-05-26", "time": "12:00" }, { "name": "MSAIN110 DL$", "size": 72177, "date": "1993-05-26", "time": "12:00" }, { "name": "MSAJU110 DL$", "size": 40080, "date": "1993-05-26", "time": "12:00" }, { "name": "OLECLI DL$", "size": 41083, "date": "1993-04-22", "time": "8:25" }, { "name": "OLESVR DL$", "size": 13129, "date": "1993-04-22", "time": "8:25" }, { "name": "ORDENTRY MD$", "size": 200396, "date": "1993-05-26", "time": "12:00" }, { "name": "README TXT", "size": 38249, "date": "1993-05-26", "time": "12:00" }, { "name": "SETUP EXE", "size": 21472, "date": "1993-05-26", "time": "12:00" }, { "name": "SETUP INI", "size": 149, "date": "1993-11-27", "time": "21:41" }, { "name": "SHARE EX$", "size": 8112, "date": "1993-04-22", "time": "8:25" }, { "name": "SHELL DL$", "size": 23296, "date": "1993-04-22", "time": "8:25" }, { "name": "SMALLB FO$", "size": 9687, "date": "1993-04-22", "time": "8:25" }, { "name": "SMALLE FO$", "size": 11236, "date": "1993-04-22", "time": "8:25" }, { "name": "SMALLF FO$", "size": 9376, "date": "1993-04-22", "time": "8:25" }, { "name": "STFSETUP EX_", "size": 584240, "date": "1993-05-26", "time": "12:00" }, { "name": "STFSETUP IN_", "size": 61043, "date": "1993-05-26", "time": "12:00" }, { "name": "VER DL$", "size": 5653, "date": "1993-04-22", "time": "8:25" }, { "name": "VER DL_", "size": 9008, "date": "1993-05-26", "time": "12:00" }, { "name": "WFWDRV TXT", "size": 2243, "date": "1993-05-26", "time": "12:00" }, { "name": "WORKGRP IN_", "size": 1955, "date": "1993-05-26", "time": "12:00" }, { "name": "SETUP IN%", "size": 149, "date": "1993-05-26", "time": "12:00" } ] } ], "volume": "DISK1" }, "2": { "dirs": [ { "path": "/", "files": [ { "name": "2 WMF", "size": 8054, "date": "1993-05-26", "time": "12:00" }, { "name": "2E WMF", "size": 7030, "date": "1993-05-26", "time": "12:00" }, { "name": "MSACCESS HL$", "size": 1189376, "date": "1993-05-26", "time": "12:00" }, { "name": "PDX110 DL$", "size": 109315, "date": "1993-05-26", "time": "12:00" }, { "name": "REGEDIT EX$", "size": 18176, "date": "1993-04-22", "time": "8:25" } ] } ], "volume": "DISK2" }, "3": { "dirs": [ { "path": "/", "files": [ { "name": "3 WMF", "size": 8950, "date": "1993-05-26", "time": "12:00" }, { "name": "3E WMF", "size": 8470, "date": "1993-05-26", "time": "12:00" }, { "name": "MSABC110 DL$", "size": 188439, "date": "1993-05-26", "time": "12:00" }, { "name": "MSAES110 DL$", "size": 16929, "date": "1993-05-26", "time": "12:00" }, { "name": "MSAFIN DL$", "size": 18558, "date": "1993-05-26", "time": "12:00" }, { "name": "PERFORM TX$", "size": 4230, "date": "1993-05-26", "time": "12:00" }, { "name": "WIZARD MD$", "size": 176477, "date": "1993-05-26", "time": "12:00" }, { "name": "MSACCESS EX$", "size": 797948, "date": "1993-05-26", "time": "12:00" }, { "name": "XBS110 DL$", "size": 153633, "date": "1993-05-26", "time": "12:00" } ] } ], "volume": "DISK3" }, "4": { "dirs": [ { "path": "/", "files": [ { "name": "4 WMF", "size": 8246, "date": "1993-05-26", "time": "12:00" }, { "name": "4E WMF", "size": 7766, "date": "1993-05-26", "time": "12:00" }, { "name": "ANALYZER MD$", "size": 49740, "date": "1993-05-26", "time": "12:00" }, { "name": "MSAJT110 DL$", "size": 384364, "date": "1993-05-26", "time": "12:00" }, { "name": "NEWCUST DB$", "size": 1212, "date": "1993-05-26", "time": "12:00" }, { "name": "NWIND MD$", "size": 563071, "date": "1993-05-26", "time": "12:00" }, { "name": "PIM HL$", "size": 8119, "date": "1993-05-26", "time": "12:00" }, { "name": "PIM MD$", "size": 109544, "date": "1993-05-26", "time": "12:00" }, { "name": "UTILITY MD$", "size": 46605, "date": "1993-05-26", "time": "12:00" }, { "name": "WINHELP EX$", "size": 147911, "date": "1993-04-22", "time": "8:26" }, { "name": "WINHELP HL$", "size": 28161, "date": "1993-04-22", "time": "8:26" } ] } ], "volume": "DISK4" }, "5": { "dirs": [ { "path": "/", "files": [ { "name": "5 WMF", "size": 4662, "date": "1993-05-26", "time": "12:00" }, { "name": "5E WMF", "size": 4150, "date": "1993-05-26", "time": "12:00" }, { "name": "CBTLIB4 DL$", "size": 11179, "date": "1993-05-26", "time": "12:00" }, { "name": "CUECARD EX$", "size": 60269, "date": "1993-05-26", "time": "12:00" }, { "name": "CUECARDS DL$", "size": 2047, "date": "1993-05-26", "time": "12:00" }, { "name": "CUECARDS LE$", "size": 887544, "date": "1993-05-26", "time": "12:00" }, { "name": "GRAPH EX$", "size": 364877, "date": "1993-04-22", "time": "8:25" }, { "name": "MSGRAPH HL$", "size": 110291, "date": "1993-04-22", "time": "8:25" } ] } ], "volume": "DISK5" }, "6": { "dirs": [ { "path": "/", "files": [ { "name": "6 WMF", "size": 3702, "date": "1993-05-26", "time": "12:00" }, { "name": "6E WMF", "size": 3222, "date": "1993-05-26", "time": "12:00" }, { "name": "ANALYZER TX$", "size": 2881, "date": "1993-05-26", "time": "12:00" }, { "name": "BTRIEVE TX$", "size": 2598, "date": "1993-05-26", "time": "12:00" }, { "name": "ERRATA TX$", "size": 2886, "date": "1993-05-26", "time": "12:00" }, { "name": "MSACCES2 HL$", "size": 1189376, "date": "1993-05-26", "time": "12:00" }, { "name": "MSACCES3 HL$", "size": 33909, "date": "1993-05-26", "time": "12:00" }, { "name": "ORDENTRY HL$", "size": 14224, "date": "1993-05-26", "time": "12:00" }, { "name": "ORDENTRY TX$", "size": 2281, "date": "1993-05-26", "time": "12:00" }, { "name": "PERFORM TX$", "size": 4230, "date": "1993-05-26", "time": "12:00" }, { "name": "WFWNET DR$", "size": 151762, "date": "1993-05-26", "time": "12:00" } ] } ], "volume": "DISK6" }, "7": { "dirs": [ { "path": "/", "files": [ { "name": "7 WMF", "size": 5846, "date": "1993-05-26", "time": "0:00" }, { "name": "7E WMF", "size": 5366, "date": "1993-05-26", "time": "0:00" }, { "name": "WFWDRV EXE", "size": 23581, "date": "1993-05-26", "time": "0:00" }, { "name": "WFWNET DR_", "size": 165600, "date": "1993-05-26", "time": "0:00" }, { "name": "COMMDLG DL_", "size": 50924, "date": "1993-05-20", "time": "0:00" }, { "name": "CTL3D DL_", "size": 9323, "date": "1993-05-26", "time": "0:00" }, { "name": "DBNMP3 DL_", "size": 6530, "date": "1993-05-26", "time": "0:00" }, { "name": "DRVORACL HL_", "size": 36234, "date": "1993-05-26", "time": "0:00" }, { "name": "DRVSSRVR HL_", "size": 71701, "date": "1993-05-26", "time": "0:00" }, { "name": "INSTCAT SQL", "size": 93834, "date": "1993-05-26", "time": "0:00" }, { "name": "ODBC DL_", "size": 25437, "date": "1993-05-26", "time": "0:00" }, { "name": "ODBC INF", "size": 1937, "date": "1993-05-26", "time": "0:00" }, { "name": "ODBCADM EX_", "size": 3946, "date": "1993-05-26", "time": "0:00" }, { "name": "ODBCINST DL_", "size": 40626, "date": "1993-05-26", "time": "0:00" }, { "name": "ODBCINST HL_", "size": 12314, "date": "1993-05-26", "time": "0:00" }, { "name": "ODBCSTP EX_", "size": 13951, "date": "1993-05-26", "time": "0:00" }, { "name": "ORA6WIN DL_", "size": 146233, "date": "1993-05-26", "time": "0:00" }, { "name": "ORACLE TXT", "size": 13914, "date": "1993-05-26", "time": "0:00" }, { "name": "SETUP EXE", "size": 24624, "date": "1993-05-26", "time": "0:00" }, { "name": "SETUP LST", "size": 416, "date": "1993-05-26", "time": "0:00" }, { "name": "SQLSRVR DL_", "size": 100640, "date": "1993-05-26", "time": "0:00" }, { "name": "SQORA DL_", "size": 84804, "date": "1993-05-26", "time": "0:00" }, { "name": "SQORASTP DL_", "size": 6874, "date": "1993-05-26", "time": "0:00" }, { "name": "VER DL_", "size": 6307, "date": "1993-05-20", "time": "0:00" }, { "name": "_MSSETUP EX_", "size": 7543, "date": "1993-05-26", "time": "0:00" }, { "name": "LANMAN21", "dir": true, "date": "1993-05-26", "time": "0:00" } ] }, { "path": "/LANMAN21", "files": [ { "name": "NETWKSTA 500", "size": 109816, "date": "1993-05-26", "time": "0:00" } ] } ], "volume": "ODBC" } }, "desc_file": "README.TXT", "desc_text": "\t ----------------------------------------\r\n\t Microsoft Access Version 1.1 README File\r\n May 1993\r\n\t ----------------------------------------\r\n\r\n\t (C) Copyright Microsoft Corporation, 1993\r\n\r\n\r\nThis document provides complementary or late-breaking\r\ninformation as a supplement to the standard Microsoft\r\nAccess documentation.\r\n\r\n\r\n------------------------\r\nHow to Use This Document\r\n------------------------\r\n\r\nTo view README on screen in Windows Notepad, maximize\r\nthe Notepad window.\r\n\r\nTo print README, open it in Windows Write, Microsoft\r\nWord, or another word processor. Then select the entire\r\ndocument and format the text in 10-point Courier before\r\nprinting.\r\n\r\n\r\n--------\r\nContents\r\n--------\r\n\r\nMicrosoft Access Q&A\r\nUsing Microsoft Access with Microsoft LAN Manager\r\nUsing Microsoft Access with Microsoft Windows for Workgroups\r\nAdditional Information on Setting Up Microsoft Access\r\n on a Network Server\r\nVersion 1.1 Setup and Custom Tool Bars and AccessWizards\r\nRunning Multiple Data Access Applications\r\nUsing SQL Server Data Installed on a Novell NetWare LAN\r\n or a Banyan Network\r\nUsing Microsoft Access to Import, Attach, or Export to \r\n Microsoft FoxPro Version 2.5 Files\r\nSetting ODBC Options in the MSACCESS.INI File\r\nInstalling the ODBC Stored Procedures (INSTCAT.SQL)\r\nAsynchronous Query Execution and ODBC Drivers\r\nORACLE Server and Null Indexes\r\nUsing Microsoft Access on Novell NetWare Servers and \r\n Banyan VINES Servers (Increasing the Number of \r\n Record Locks)\r\nSetting Up Microsoft Access with a Microsoft License Pak\r\nEnhancing Performance\r\nInstalling International Versions of Cue Cards\r\nUsing Sample Applications\r\nAnalyzing Database Structure\r\nSolving Problems Printing Forms and Reports\r\nUpdated SQL Pass Through DLL and Data Definition Language DLL\r\nAvailable Disk Space\r\nUsing DECOMP.EXE to Decompress Microsoft Access Files\r\nOutdated Version 1.0 Files\r\nMicrosoft Access Files\r\n\r\nIMPORTANT: The errata and omissions in Microsoft Access \r\ndocumentation are contained in ERRATA.TXT in the Microsoft \r\nAccess program directory.\r\n\r\n\r\n--------------------\r\nMicrosoft Access Q&A\r\n--------------------\r\n\r\nThe Microsoft Access Help file includes answers for the most \r\nfrequently asked questions about Microsoft Access. To view \r\nthese, click Product Support in the Microsoft Access Help \r\nTable of Contents, and then click Common Questions and Answers \r\nin the Microsoft Access Product Support topic.\r\n\r\n-------------------------------------------------\r\nUsing Microsoft Access with Microsoft LAN Manager\r\n-------------------------------------------------\r\n\r\nThe following problem may occur when using products based \r\non Microsoft LAN Manager versions prior to 2.2 on your\r\nMS-DOS or PC-DOS workstation.\r\n\r\nUsing Microsoft Access on an MS-DOS or PC-DOS workstation \r\nrunning a product based on versions of Microsoft LAN Manager \r\nprior to version 2.2 can irreparably corrupt a database file. \r\nDatabase corruption is most likely to occur when a user \r\nworkstation operates faster than the file server storing \r\nthe database file. (Note that the CPU speed alone does not \r\ndetermine the operation speed of the server. Heavy network \r\ntraffic can make the server operate more slowly than a user \r\nworkstation(s).)\r\n\r\nProducts that may be affected include:\r\n \r\n DEC Pathworks for DOS version 4.1 \r\n Microsoft LAN Manager prior to version 2.2\r\n NCR StarGroup LAN Manager version 3.6\r\n Olivetti Olinet LAN Manager version 2.1\r\n Ungermann-Bass LAN Manager version 2.1\r\n\r\nSee your network administrator to find out if the information\r\nin this section applies to your network software.\r\n\r\nTo prevent data corruption when using the enhanced version\r\nof Microsoft LAN Manager version 2.1 or 2.1a, your network \r\nadministrator should install the Hotfix that is included \r\non the ODBC disk.\r\n\r\nTo determine your version of Microsoft LAN Manager:\r\n\r\n> Type net ver at the command prompt to determine which\r\n version of LAN Manager is installed on the user workstation.\r\n You will see information such as the following:\r\n\r\n C:\\>NET VER\r\n Microsoft LAN Manager Version 2.1.0\r\n DOS Enhanced Workstation\r\n Created at 11-15-91 07:27am\r\n\r\nProceed to the procedure, \"To install the Hotfix on each \r\nuser workstation,\" only if the command reports you are \r\nusing Microsoft LAN Manager version 2.1 or 2.1a.\r\n\r\nIf the command does not report which version of Microsoft\r\nLAN Manager you are using, you are using a version earlier\r\nthan 2.1. You need to upgrade the workstation to Microsoft LAN \r\nManager version 2.2 or follow the procedure, \"To adapt a \r\nworkstation using a version of Microsoft LAN Manager prior to \r\n2.1,\" at the end of this section.\r\n\r\nIMPORTANT: If you are using network software based on Microsoft \r\nLAN Manager and aren't sure which version of Microsoft LAN \r\nManager it corresponds to, do not install the Hotfix. Instead,\r\nfollow the procedure, \"To adapt a workstation using a version \r\nof Microsoft LAN Manager prior to 2.1.\" You can install the \r\nHotfix later if it's determined you need it.\r\n\r\nTo install the Hotfix on each user workstation:\r\n\r\n1 Type ver at the command prompt to determine which\r\n version of MS-DOS is installed on the user workstation.\r\n\r\n2 Insert the ODBC disk in drive A.\r\n\r\n3 Copy the appropriate NETWKSTA file on the ODBC Setup disk \r\n to the LAN Manager NETPROG directory and rename the file \r\n NETWKSTA.EXE. You should use the NETWKSTA.500 file for both \r\n MS-DOS version 5.0 and MS-DOS version 6.0. For example, if \r\n LAN Manager is currently installed in the LANMAN.DOS \r\n directory on drive C, and you are using MS-DOS version \r\n 5.0, type:\r\n\r\n copy a:netwksta.500 c:\\lanman.dos\\netprog\\netwksta.exe\r\n\r\n If you are using MS-DOS version 3.3 or 4.0, you must contact\r\n Microsoft Product Support Services to request the appropriate\r\n NETWKSTA file. In the United States, call Microsoft LAN Manager\r\n Product Support Services at (206) 635-7020.\r\n\r\n4 Reboot the user workstation.\r\n\r\nTo adapt a workstation using a version of Microsoft LAN Manager \r\nearlier than 2.1:\r\n\r\n> To prevent database corruption when using versions of Microsoft \r\n LAN Manager earlier than version 2.1, turn write-behind off by \r\n adding or modifying the following line in the [workstation] \r\n section of your LANMAN.INI file:\r\n\r\n [workstation]\r\n wrkheuristics=X0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\r\n\r\nNOTE: The Xs are placeholders for values in the range of 0-2. \r\nIn all, there should be 33 values in this entry, and the second \r\nvalue must be 0 (zero). See your Microsoft LAN Manager \r\nAdministrator's Reference for details.\r\n\r\nIMPORTANT: If this line already exists in your LANMAN.INI file, \r\nchange only the second value to 0 (zero).\r\n\r\nNote that adding this line may slightly decrease the \r\nperformance of your system.\r\n\r\nYou can also resolve this problem by upgrading to LAN Manager\r\nversion 2.2 or later. For details, please contact your network\r\nvendor or Microsoft Product Support at the numbers listed in your \r\nMicrosoft Access User's Guide or in Microsoft Access Help. (From \r\nthe Help menu, choose Contents, and then click Product Support.)\r\n\r\n\r\n------------------------------------------------------------\r\nUsing Microsoft Access with Microsoft Windows for Workgroups\r\n------------------------------------------------------------\r\n\r\nIMPORTANT: Read this topic before you use Microsoft Access \r\nwith Microsoft Windows for Workgroups.\r\n\r\nWhile running Microsoft Windows for Workgroups, if you use the \r\nNetwork button in Microsoft Access dialog boxes to connect \r\nto a password-protected server, you may lose data. To avoid \r\ndamaging your database, you must install the updated Microsoft \r\nWindows for Workgroups driver included with Microsoft Access. \r\nUntil you have installed this driver, do not use the Network\r\nbutton in Microsoft Access dialog boxes to make network \r\nconnections. \r\n\r\nNOTE: If you are considering installing Windows for Workgroups \r\nat a later date, install the updated driver now.\r\n\r\nTo install the updated Windows for Workgroups driver:\r\n\r\n1 Exit Microsoft Windows or Windows For Workgroups. \r\n\r\n This driver cannot be installed while you are running \r\n Microsoft Windows.\r\n\r\n2 Insert the ODBC disk in drive A.\r\n\r\n3 Type a: and then press the Enter key to switch to drive A.\r\n\r\n4 Type wfwdrv if Windows is installed on your PC and is in the\r\n PATH statement in your AUTOEXEC.BAT file. Otherwise, do one of \r\n the following: \r\n\r\n * If Windows is installed on your PC but is not in the\r\n PATH statement in AUTOEXEC.BAT, type the path where \r\n Windows is installed. For example, type: \r\n \r\n wfwdrv c:\\windows.\r\n\r\n * If Windows is installed on the network, specify the system \r\n directory where USER.EXE is found. For example, to install \r\n the driver in the Q:\\SYSTEM directory, type: \r\n\r\n wfwdrv q:\\system \r\n\r\n The Windows for Workgroups driver is installed.\r\n\r\n5 Type win to restart Windows.\r\n\r\nIf you have any questions about this driver, please contact \r\nMicrosoft Product Support Services for Windows for Workgroups.\r\n\r\n-----------------------------------------------------\r\nAdditional Information on Setting Up Microsoft Access\r\non a Network Server\r\n-----------------------------------------------------\r\n\r\nTo set up Microsoft Access on a network server, you must run\r\nSetup /a from floppy disks. Do not copy the files to a hard\r\ndisk and run Setup /a from there. Unless you run Setup /a\r\nfrom floppy disks, Microsoft Access won't be properly\r\nconfigured on the network server, and users won't be able to\r\nset up their workstations from the server using Setup /n.\r\n\r\nIf you received Microsoft Access on a compact disc and want\r\nto set it up on a network server, you must copy the disk\r\nimages to floppy disks and run Setup /a from the floppy disks.\r\nIf you're setting up Microsoft Access on a local machine, you \r\ncan run Setup directly from the compact disc.\r\n\r\n\r\n--------------------------------------------------------\r\nVersion 1.1 Setup and Custom Tool Bars and AccessWizards\r\n--------------------------------------------------------\r\n\r\nMicrosoft Access version 1.1 includes updated UTILITY.MDA \r\nand WIZARD.MDA files. If you have modified either of these \r\nlibrary databases -- by creating custom tool bars or adding \r\ncustom AccessWizards, for example -- you should make backup \r\ncopies of these files before installing Microsoft Access \r\nversion 1.1. Then modify the version 1.1 copies of the files \r\nto include your changes.\r\n\r\n\r\n-----------------------------------------\r\nRunning Multiple Data Access Applications\r\n-----------------------------------------\r\n\r\nMicrosoft Access, Microsoft Access custom applications, \r\nMicrosoft Visual Basic version 3.0, and Visual Basic custom \r\napplications all use the same database engine to perform \r\ntheir database-related operations. If one or more of these \r\nare running simultaneously, you must be sure that all \r\nsections and entries from the initialization (.INI) file \r\nthat are used for data manipulation (the entries in the \r\n[Installable ISAMs], [Paradox ISAM], and [dBASE ISAM] \r\nsections) are included in the initialization file for each \r\napplication. This ensures that you can use data in other \r\nformats or applications, such as FoxPro, dBASE, or Paradox.\r\n\r\nIf two or more applications that use the database engine \r\nare running simultaneously, the engine is initialized to\r\nthe .INI file settings of the application that was \r\nstarted first. \r\n\r\nIf the entries in the three data manipulation sections are \r\nnot included in the .INI file of the first application that \r\nstarts the database engine, then no application that uses \r\nthe engine will be able to use FoxPro, dBASE, or Paradox \r\ndata while the first application is running.\r\n\r\nFor example, when you start Microsoft Access, it initializes \r\nthe database engine according to the settings in the \r\nMSACCESS.INI file. If you then start Visual Basic version 3.0 \r\nwhile Microsoft Access is still running, the database engine \r\nwill use the MSACCESS.INI file settings rather than the \r\nsettings in the Visual Basic initialization file.\r\n\r\nThe list below shows where each application looks for its \r\ninitialization information: \r\n\r\nApplication .INI file\r\n----------- ---------\r\nMicrosoft Access MSACCESS.INI\r\nMicrosoft Access application .INI\r\nVisual Basic at design time VB.INI\r\nVisual Basic at run time VB.INI\r\nVisual Basic .EXE application .INI\r\n\r\n\r\n-------------------------------------------------------\r\nUsing SQL Server Data Installed on a Novell NetWare LAN\r\n or a Banyan Network\r\n-------------------------------------------------------\r\n\r\nIf you use Microsoft Access on a workstation running under \r\nMicrosoft Windows for Workgroups and want to access SQL \r\nServer data installed on a Novell NetWare LAN or a Banyan\r\nnetwork, you must use the SQL Server Network Integration Kit\r\n(NIK). For details, see your Network Integration Kit and\r\nSQL Server documentation. If you still have questions,\r\ncontact Microsoft Product Support at one of the numbers \r\nlisted in the Microsoft Access User's Guide or in Microsoft\r\nAccess Help. (From the Help menu, choose Contents, and then\r\nclick Product Support.)\r\n\r\n\r\n------------------------------------------------------\r\nUsing Microsoft Access to Import, Attach, or Export to \r\n Microsoft FoxPro Version 2.5 Files\r\n------------------------------------------------------\r\n\r\nFoxPro version 2.5 doesn't distinguish between tables \r\ncreated with the MS-DOS version and those created with the \r\nMicrosoft Windows version. Data in tables created with FoxPro \r\nversion 2.5 for MS-DOS is stored in OEM format. Data in tables \r\ncreated with FoxPro version 2.5 for Windows is stored in ANSI \r\nformat. Microsoft Access converts all FoxPro version 2.5 data \r\nfrom an OEM code page to the ANSI 1252 code page when importing \r\nor attaching FoxPro 2.5 data, and it converts the ANSI code \r\npage to an OEM code page when exporting to FoxPro 2.5 tables. \r\nThe result is that extended characters in tables created with \r\nFoxPro version 2.5 for Windows aren't converted properly.\r\n\r\nIf your FoxPro version 2.5 tables contain extended characters, \r\nyou should be certain that the tables are stored in OEM format \r\n(that is, created by FoxPro version 2.5 for MS-DOS). FoxPro \r\nversion 2.5a will be able to identify the code page format of \r\nthe data, enabling Microsoft Access to correctly determine how \r\nto convert extended characters. For information on FoxPro version\r\n2.5a, please contact Microsoft End-User Sales at (800) 426-9400.\r\n\r\n\r\n---------------------------------------------\r\nSetting ODBC Options in the MSACCESS.INI File\r\n---------------------------------------------\r\n\r\nThe following table lists all the valid entries applying \r\nto ODBC that can appear in the Microsoft Access initialization \r\nfile, MSACCESS.INI. They appear in the [Debug] and [ODBC] \r\nsections.\r\n\r\nEntry Value Effect\r\n------- ----- ------\r\nSection: [Debug]\r\nRmtTrace 0 Use asynchronous query execution \r\n if possible; no ODBC API tracing \r\n (default).\r\n 8 Trace ODBC API calls in ODBCAPI.TXT \r\n in the Microsoft Access directory.\r\n 16 Force synchronous query execution.\r\n 24 Trace ODBC API calls; force \r\n asynchronous query execution.\r\nSection: [ODBC]\r\nTraceSQLMode 0 No tracing of SQL queries (default).\r\n 1 Trace SQL queries sent to ODBC in \r\n SQLOUT.TXT in the Microsoft Access \r\n directory.\r\nQueryTimeout S Wait S seconds for queries sent to \r\n ODBC, and then stop trying to process \r\n the query results (for asynchronous \r\n queries only). (Default: 60 seconds).\r\nLoginTimeout S Wait S seconds for ODBC login response, \r\n and then stop trying to connect to a\r\n server. (Default: 20 seconds).\r\nConnectionTimeout S Wait S seconds, and then close idle \r\n ODBC connections. (Default: 600 \r\n seconds).\r\nAsyncRetryInterval M Retry asynchronous queries every M \r\n milliseconds. (Default: 500 \r\n milliseconds).\r\nAttachCaseSensitive 0 Attach the first table whose name \r\n matches the specified string, \r\n regardless of case.\r\n 1 Attach a table only if its name \r\n exactly matches the specified string.\r\nAttachableObjects string A list of object types you can attach. \r\n (Default: 'TABLE','VIEW','SYSTEM TABLE',\r\n 'ALIAS', 'SYNONYM'.)\r\nSnapshotOnly 0 Get index information when tables are \r\n attached so that dynasets are allowed \r\n (default).\r\n 1 Ignore index information when tables \r\n are attached so that only snapshots \r\n are allowed.\r\n\r\n\r\n---------------------------------------------------\r\nInstalling the ODBC Stored Procedures (INSTCAT.SQL)\r\n---------------------------------------------------\r\n\r\nMicrosoft Access version 1.1 contains a new version of the \r\nODBC stored procedures (found in the INSTCAT.SQL file), \r\nwhich must be installed on a SQL Server before you can \r\naccess data from that server. However, the INSTCAT.SQL file \r\nthat comes with version 1.1 can't be used with version 1.0 of \r\nMicrosoft Access. If you have Microsoft Access version 1.0 and \r\nattempt to attach a table from a database on a SQL Server where \r\nversion 1.1 of the ODBC stored procedures have been installed, \r\nyou will see this error message:\r\n\r\n \"'.' isn't a valid name.\"\r\n\r\nTo fix this problem, you should update all of the computers \r\non your network to version 1.1 of Microsoft Access and \r\ninstall version 1.1 of INSTCAT.SQL on your SQL Servers.\r\n\r\nIf you have Sybase SQL Server databases, you MUST upgrade \r\nall users to Microsoft Access 1.1 and use the version 1.1 \r\nINSTCAT.SQL, which contains fixes that are required for \r\nSybase SQL Server databases. If you have Microsoft SQL \r\nServer databases and have a mixture of Microsoft Access 1.0 \r\nand 1.1 installations, you can use the version 1.0 \r\nINSTCAT.SQL until all users are upgraded to Microsoft Access\r\nversion 1.1.\r\n\r\nThe version 1.1 INSTCAT.SQL file is also included with \r\nMicrosoft Visual Basic version 3.0. If you are using this \r\nversion of Visual Basic and want to access SQL Server \r\ndatabases from both Visual Basic and Microsoft Access, you \r\nshould either update all of your users to Microsoft Access \r\nversion 1.1 or use the version 1.0 INSTCAT.SQL instead of \r\nthe version supplied with Visual Basic. Visual Basic version\r\n3.0 will work correctly with the version 1.0 INSTCAT.SQL,\r\nexcept that it will be unable to delete indexes from tables.\r\n\r\n\r\n---------------------------------------------\r\nAsynchronous Query Execution and ODBC Drivers\r\n---------------------------------------------\r\n\r\nWhen executing queries against Open Database Connectivity \r\n(ODBC) data sources, Microsoft Access will attempt, if \r\nsupported by the ODBC driver, to execute the query \r\nasynchronously. The client-server network libraries \r\nsupported by some ODBC drivers may experience difficulties \r\nwhile executing queries asynchronously. If you encounter \r\nproblems with query execution, you can disable asynchronous \r\nexecution by adding the following entry to the [Debug] \r\nsection of your MSACCESS.INI file:\r\n RmtTrace=16\r\n\r\n\r\n------------------------------\r\nORACLE Server and Null Indexes\r\n------------------------------\r\n\r\nSome databases, such as ORACLE Server databases, allow \r\nmultiple Null primary keys in an index, although the index \r\nis still considered unique. Microsoft Access can't modify \r\nrecords that have multiple occurrences of the same unique \r\n(Null) value, although it can modify other records in the \r\ntable.\r\n\r\nIf you want to modify records in such a database, make sure \r\nthat each record has a unique primary key and that no more \r\nthan one of these is Null.\r\n\r\n\r\n------------------------------------------------------------\r\nUsing Microsoft Access on Novell NetWare Servers and Banyan \r\n VINES Servers (Increasing the Number of Record Locks)\r\n------------------------------------------------------------\r\n\r\nOn Novell NetWare Servers:\r\n\r\nIf you are attempting to use large Microsoft Access \r\ndatabases on a Novell NetWare server, set the \"maximum \r\nrecord locks per connection\" to the largest allowable \r\nvalue (10,000). The execution of large bulk operations \r\nin Microsoft Access (such as a large update query) can \r\ncause the server to run out of record lock connections. \r\nIf you don't set the number of record locks to the maximum \r\nvalue while using Microsoft Access, it could result in \r\nthe loss of data due to a server crash.\r\n\r\nSee your Novell NetWare documentation for a description of \r\nhow to set the number of record locks.\r\n\r\nOn Banyan VINES Servers:\r\n\r\nIf you are attempting to use large Microsoft Access \r\ndatabases on a Banyan VINES server, you may exceed the \r\nnumber of record locks allowed. (Note that the number of \r\nrecord locks is not user-definable for Banyan VINES\r\nservers.)\r\n\r\nBanyan VINES version 4.11 allows a maximum of 500 record \r\nlocks. It is conceivable that a large Microsoft Access bulk \r\noperation would require that many record locks. Banyan VINES\r\nversion 5.00 allows only 100 record locks, which would \r\nseverely limit Microsoft Access use. Banyan VINES version \r\n5.5 allows at least 10,000 record locks.\r\n\r\n\r\n--------------------------------------------------------\r\nSetting Up Microsoft Access with a Microsoft License Pak\r\n--------------------------------------------------------\r\n\r\nThe first time you install Microsoft Access using the\r\nMicrosoft License Pak, Setup stores the company name but \r\nnot the user name. Setup customizes the user name for each\r\ninstallation. \r\n\r\nTo install Microsoft Access using the Microsoft License \r\nPak:\r\n\r\n1 In the Windows Program Manager, choose Run from the File \r\n menu. \r\n2 In the Command Line box, type setup /l where \r\n is the directory in which the Microsoft Access \r\n program files are stored. (Note that l is the letter l, \r\n not the number one).\r\n For example, if your Microsoft Access files are on \r\n drive C in a directory called ACCESS, you'd type \r\n c:\\access\\setup /l in this box.\r\n\r\n---------------------\r\nEnhancing Performance\r\n---------------------\r\n\r\nFor information on increasing the buffer space, read the \r\nPERFORM.TXT file in your Microsoft Access directory. This \r\nfile also desribes other ways of tuning Microsoft Access \r\nto get the best performance.\r\n\r\n\r\n----------------------------------------------\r\nInstalling International Versions of Cue Cards\r\n----------------------------------------------\r\n\r\nYou will not be able to use Cue Cards if you install it \r\nin a directory whose name contains a ligature, such as the \r\ncharacters ▀ and µ. To resolve this problem, delete all the \r\nMicrosoft Access files and remove the directory. Then rerun \r\nMicrosoft Access Setup.\r\n\r\n\r\n-------------------------\r\nUsing Sample Applications\r\n-------------------------\r\n\r\nIn addition to the Northwind Traders database (NWIND.MDB), \r\nwhich is used in examples throughout the Microsoft Access \r\ndocumentation, you can install two sample applications:\r\nPersonal Information Manager (PIM.MDB) and Order Entry \r\n(ORDENTRY.MDB). These are just two examples of the types \r\nof applications you can create with Microsoft Access. You \r\ncan use them as a learning tool for creating your own \r\napplications -- and perhaps in your daily work and business\r\nas well.\r\n\r\nIf you chose the Complete Installation option when you \r\ninstalled Microsoft Access, the Setup program installed the \r\nsample application files. If you made a different choice or \r\nif you have removed the files, you can install them by running \r\nSetup again, choosing Custom Installation, and selecting \r\nSample files. Setup installs the files in the program \r\ndirectory.\r\n\r\nGeneral information and instructions on using each \r\napplication are available online for the Personal Information \r\nManager and Order Entry applications. To use this information, \r\nstart Microsoft Access and open the database file for the \r\napplication. Then press F1 or choose Contents from the Help \r\nmenu. \r\n\r\nNOTE: The Personal Information Manager and Order Entry \r\napplications are designed to be run on a VGA or SVGA monitor \r\nonly.\r\n\r\n\r\n----------------------------\r\nAnalyzing Database Structure\r\n----------------------------\r\n\r\nWhen you develop a new database or modify an existing one, you'll \r\nprobably want detailed information about its structure. Microsoft \r\nProduct Support Services provides an informal diagnostic tool for \r\nthis purpose called the Database Analyzer. Using this tool, you \r\ncan display or print tables listing the structural features of \r\nmany of the objects in a database. For information on installing \r\nand using the Database Analyzer, read the ANALYZER.TXT file found\r\nin your Microsoft Access program directory.\r\n\r\n\r\n-------------------------------------------\r\nSolving Problems Printing Forms and Reports\r\n-------------------------------------------\r\n\r\nMicrosoft Access forms or reports, because of a driver problem, \r\nmay not print correctly on an HP LaserJet IIISi printer using \r\nnon-TrueType fonts. For best results, use TrueType fonts with \r\nthis printer.\r\n\r\n\r\n------------------------------------------------\r\nUpdated SQL Pass Through DLL and Data Definition \r\nLanguage DLL\r\n------------------------------------------------\r\n\r\nThe SQL Pass Through DLL and Data Definition Language DLL \r\nhave been updated for Microsoft Access version 1.1. If you\r\nare currently using version 1.0 of either of these DLLs \r\n(SPT.DLL or MSADDL10.DLL), you must upgrade to the version \r\n1.1 DLLs (MSASP110.DLL and MSADDL11.DLL). You can download \r\nthe version 1.1 DLLs from the MSACCESS forum on CompuServe. \r\nSupport for these DLLs is provided on CompuServe only.\r\n\r\n--------------------\r\nAvailable Disk Space\r\n--------------------\r\n\r\nThe DBLSPACE utility supplied with MS-DOS version 6.0 \r\n(as well as other similar disk compression utilities) \r\nenables you to set a compression ratio, which affects \r\nthe amount of disk space that commands like the MS-DOS \r\ncommand DIR report as available. For example, if you \r\nhave 5 megabytes of actual disk space, but you've set \r\nthe compression ratio to 20:1, DIR will report that you \r\nhave 100 MB of free space. You can use the compression \r\nratio to approximate the amount of room you have for \r\ncompressed files on your hard disk.\r\n\r\nHowever, different kinds of files actually compress at \r\ndifferent ratios. For example, the Microsoft Access .EXE \r\nfile, Help files, and DLLs compress at a ratio closer to \r\n1.5:1. Although DIR may report that you have enough disk \r\nspace to install Microsoft Access, there might not be \r\nenough room to fully install all the Microsoft Access files.\r\n\r\nIf you run out of disk space when installing Microsoft \r\nAccess, you can free disk space by deleting unnecessary files. \r\nYou can also use the Custom Setup option during Microsoft \r\nAccess Setup, and select only the minimal set of files \r\nyou need to run Microsoft Access (for example, you can \r\nchoose not to install Cue Cards or the Help file).\r\n\r\nYou may also want to adjust your compression ratio if you \r\nfind you are running out of disk space when DIR tells you \r\nthat you have enough.\r\n\r\n-----------------------------------------------------\r\nUsing DECOMP.EXE to Decompress Microsoft Access Files\r\n-----------------------------------------------------\r\n\r\nMicrosoft Access includes a decompression utility, \r\nDECOMP.EXE. You can use DECOMP.EXE to decompress files \r\nwithout running Setup. This allows you to install \r\nindividual Microsoft Access files. DECOMP.EXE uses the \r\nfollowing syntax:\r\n\r\n DECOMP [/A /F /Q] []\r\n\r\nThe argument specifies the file or files to be \r\ndecompressed; it can be a file name or a wildcard pattern. \r\nThe argument is the name of the decompressed \r\nfile or directory. \r\n\r\nThe following table summarizes the decompression utility \r\ncommand-line options.\r\n\r\nOption Description\r\n------ -----------\r\n/A Appends the decompressed version of the source \r\n file to the file specified by .\r\n/F Forces overwriting of the file specified by \r\n .\r\n/Q Calculates the size of the uncompressed file \r\n (no output).\r\n\r\n\r\n--------------------------\r\nOutdated Version 1.0 Files\r\n--------------------------\r\n\r\nIf you are installing Microsoft Access version 1.1 in the \r\nsame directory as an existing copy of version 1.0, the \r\nMicrosoft Access Setup program installs the version 1.1 \r\nfiles and at the same time deletes or replaces outdated \r\nversion 1.0 files.\r\n\r\nThe following files are no longer used by Microsoft Access, \r\nand are deleted by Setup:\r\n\r\n BTRVISAM.DLL\r\n DBSISAM.DLL\r\n MSABC100.DLL\r\n MSAES100.DLL\r\n MSAIN100.DLL\r\n MSAJU100.DLL\r\n MSAJT100.DLL\r\n PDXISAM.DLL\r\n README_.TXT (deleted only if you start Setup by typing \r\n setup /a)\r\n \r\nFor a complete list of the version 1.1 files, see the \r\n\"Microsoft Access Files\" section in this README file.\r\n\r\n\r\n----------------------\r\nMicrosoft Access Files\r\n----------------------\r\n\r\nFile name Destination Description\r\n--------- ----------- -----------\r\n1.wmf N/A Billboard displayed during \r\n setup. VGA and higher \r\n resolution.\r\n1e.wmf N/A Billboard displayed during \r\n setup. EGA resolution.\r\n2.wmf N/A Billboard displayed during \r\n setup. VGA and higher \r\n resolution.\r\n2e.wmf N/A Billboard displayed during \r\n setup. EGA resolution.\r\n3.wmf N/A Billboard displayed during \r\n setup. VGA and higher \r\n resolution.\r\n3e.wmf N/A Billboard displayed during \r\n setup. EGA resolution.\r\n4.wmf N/A Billboard displayed during \r\n setup. VGA and higher \r\n resolution.\r\n4e.wmf N/A Billboard displayed during \r\n setup. EGA resolution.\r\n5.wmf N/A Billboard displayed during \r\n setup. VGA and higher \r\n resolution.\r\n5e.wmf N/A Billboard displayed during \r\n setup. EGA resolution.\r\n6.wmf N/A Billboard displayed during \r\n setup. VGA and higher \r\n resolution.\r\n6e.wmf N/A Billboard displayed during \r\n setup. EGA resolution.\r\n7.wmf N/A Billboard displayed during \r\n setup. VGA and higher \r\n resolution.\r\n7e.wmf N/A Billboard displayed during \r\n setup. EGA resolution.\r\n8.wmf N/A Billboard displayed during \r\n setup. VGA and higher \r\n resolution.\r\n8e.wmf N/A Billboard displayed during \r\n setup.EGA resolution.\r\nanalyzer.md$ Microsoft Access Product \r\n Support Services utility.\r\nanalyzer.tx$ PSS Analyzer utility readme.\r\nbtrieve.tx$ Information about configuring \r\n Btrieve for use with Microsoft \r\n Access.\r\nbtrv110dl$ Btrieve ISAM DLL.\r\ncbtlib4.dl$ Cue Cards DLL.\r\ncommdlg.dl$ Common dialog boxes. This is a \r\n file shipped with Windows \r\n version 3.1.\r\ncommdlg.dl_ N/A Uncompressed version of common \r\n\t\t\t\t dialog boxes used by Setup \r\n program.\r\nctl3d.dl$ 3D-look DLL.\r\ncuecard.ex$ Cue Cards executable.\r\ncuecards.dl$ Cue Cards communication DLL.\r\ncuecards.le$ Cue Cards lesson file.\r\nddeml.dl$ DDE support DLL.\r\ndecomp.exe N/A Utility to individually \r\n decompress files on the Microsoft \r\n Access disks.\r\ndetcmd.dl_ DLL used by Setup.\r\nerrata.tx$ Microsoft Access documentation\r\n\t\t\t\t errata file. Contains late \r\n changes to documentation.\r\ngraph.ex$ \r\nmsabc110.dl$ Microsoft Access Basic code DLL.\r\nmsacces2.hl$ Part 2 of the Microsoft Access \r\n\t\t\t\t Help file.\r\nmsaccess.ex$ Microsoft Access executable.\r\nmsaccess.hl$ Part 1 of the Microsoft Access \r\n\t\t\t\t Help file.\r\nmsaccess.in$ Microsoft Access initialization\r\n\t\t\t\t file.\r\nmsaccess.re$ N/A Input file for additions Setup \r\n\t\t\t\t makes to the OLE registration \r\n\t\t\t\t database.\r\nmsaes110.dl$ Microsoft Access expression \r\n\t\t\t\t service DLL.\r\nmsafin.dl$ Additional financial functions \r\n\t\t\t\t DLL.\r\nmsain110.dl$ International resources for \r\n\t\t\t\t Microsoft Access.\r\nmsajt110.dl$ Microsoft Access JET engine.\r\nmsaju110.dl$ Microsoft Access JET engine \r\n\t\t\t\t utilities.\r\nmsgraph.hl$ <\\Windows\\MSApps\\ Microsoft Graph Help file.\r\n\t MSGraph> \r\nnewcust.db$ Sample dBASE file used in \r\n\t\t\t\t Getting Started.\r\nnwind.md$ Northwind Traders sample \r\n\t\t\t\t database.\r\nolecli.dl$ OLE Client support DLL.\r\nolesvr.dl$ OLE Server support DLL.\r\nordentry.hl$ Order Entry sample application \r\n\t\t\t\t Help file.\r\nordentry.md$ Order Entry sample application \r\n\t\t\t\t database.\r\nordentry.tx$ Order Entry sample application \r\n\t\t\t\t readme.\r\npdx110.dl$ Paradox version 3.5 ISAM DLL.\r\nperform.tx$ Performance tips.\r\npim.hl$ Personal Information Manager \r\n\t\t\t\t Help file.\r\npim.md$ Personal Information Manager \r\n\t\t\t\t database.\r\nreadme.txt Microsoft Access readme file \r\n (this file.) Contains issues \r\n you should be aware of. \r\nregedit.ex$ Windows version 3.1 registration \r\n database editor.\r\nsetup.exe N/A Setup executable.\r\nsetup.ini Setup initialization file.\r\nshare.ex$ MS-DOS 5.0 file locking utility. \r\n\t\t\t\t (Not installed if already \r\n\t\t\t\t present.)\r\nshell.dl$ Windows version 3.1 utility DLL.\r\nsmallb.fo$ Required font for Microsoft \r\n\t\t\t\t Access.\r\nsmalle.fo$ Required font for Microsoft \r\n\t\t\t\t Access.\r\nsmallf.fo$ Required font for Microsoft \r\n\t\t\t\t Access.\r\nstfsetup.ex_ Microsoft Access second-level \r\n Setup executable. Also used by \r\n Change Workgroup utility.\r\nstfsetup.in_ N/A Microsoft Access second-level \r\n Setup initialization file.\r\nutility.md$ Microsoft Access utility database.\r\nver.dl$ Windows 3.1 version checking DLL.\r\nver.dl_ N/A Uncompressed version of Windows \r\n\t\t\t\t 3.1 version checking DLL used \r\n\t\t\t\t during setup.\r\nwfwdrv.exe N/A Utility to update Windows for\r\n Workgroups driver.\r\nwfwdrv.txt N/A Information about Windows for\r\n Workgroups driver.\r\nwfwnet.dr$ Windows for Workgroups driver.\r\nwfwnet.dr_ N/A Windows for Workgroups driver\r\n installed by WFWDRV.EXE.\r\nwinhelp.ex$ Windows version 3.1 Help \r\n executable.\r\nwinhelp.hl$ Windows version 3.1 Help \r\n program Help file.\r\nwizard.md$ Microsoft Access AccessWizards.\r\nworkgrp.in_ Microsoft Access workgroup \r\n\t\t\t\t initialization file used during \r\n\t\t\t\t setup. Renamed STFSETUP.INF.\r\nxbs110.dl$ FoxPro and dBASE ISAM DLL.\r\n\r\nNOTE: In the Destination column, the name in brackets indicates \r\nthe most common name for this directory; however, the directory \r\nname on your machine may be different. For example, your Windows \r\ndirectory may be called WIN31 or just WIN. The name \r\nindicates the directory where your Microsoft Access program files \r\nare stored." }