Liren Large Software Subsidy 6

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

/ Liren Large Software Subsidy 6 / 06.iso / a / a563 / 3.ddi / README.TXT < prev next >

Wrap

Text File | 1993-05-26 | 33.3 KB | 814 lines

---------------------------------------- Microsoft Access Version 1.1 README File May 1993 ---------------------------------------- (C) Copyright Microsoft Corporation, 1993 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 Additional Information on Setting Up Microsoft Access on a Network Server Version 1.1 Setup and Custom Tool Bars and AccessWizards Running Multiple Data Access Applications Using SQL Server Data Installed on a Novell NetWare LAN or a Banyan Network Using Microsoft Access to Import, Attach, or Export to Microsoft FoxPro Version 2.5 Files Setting ODBC Options in the MSACCESS.INI File Installing the ODBC Stored Procedures (INSTCAT.SQL) Asynchronous Query Execution and ODBC Drivers ORACLE Server and Null Indexes Using Microsoft Access on Novell NetWare Servers and Banyan VINES Servers (Increasing the Number of Record Locks) Setting Up Microsoft Access with a Microsoft License Pak Enhancing Performance Installing International Versions of Cue Cards Using Sample Applications Analyzing Database Structure Solving Problems Printing Forms and Reports Updated SQL Pass Through DLL and Data Definition Language DLL Available Disk Space Using DECOMP.EXE to Decompress Microsoft Access Files Outdated Version 1.0 Files Microsoft Access Files -------------------- Microsoft Access Q&A -------------------- The Microsoft Access version 1.1 Upgrade Help file includes answers for the most frequently asked questions about Microsoft Access. To view these, click Common Questions and Answers at the beginning of the "What's New in Microsoft Access Version 1.1" topic. ------------------------------------------------- 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: > Type net ver at the command 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 command 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 Setup disk to the LAN Manager NETPROG directory and rename the file NETWKSTA.EXE. You should use the NETWKSTA.500 file for both MS-DOS version 5.0 and MS-DOS version 6.0. For example, if LAN Manager is currently installed in the LANMAN.DOS directory on drive C, and you are using MS-DOS version 5.0, type: copy a:netwksta.500 c:\lanman.dos\netprog\netwksta.exe If you are using MS-DOS version 3.3 or 4.0, you must contact Microsoft Product Support Services to request the appropriate NETWKSTA file. In the United States, call Microsoft LAN Manager Product Support Services at (206) 635-7020. 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. (From the Help menu, choose Contents, and then click Product Support.) ------------------------------------------------------------ Using Microsoft Access with Microsoft Windows for Workgroups ------------------------------------------------------------ IMPORTANT: Read this topic 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: and then press the Enter key to switch to drive A. 4 Type wfwdrv if Windows is installed on your PC and is in the PATH statement in your AUTOEXEC.BAT file. Otherwise, do one of the following: * If Windows is installed on your PC but is not in the PATH statement in AUTOEXEC.BAT, type the path where Windows is installed. For example, type: 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 in the Q:\SYSTEM directory, type: wfwdrv q:\system The Windows for Workgroups driver is installed. 5 Type win to restart Windows. If you have any questions about this driver, please contact Microsoft Product Support Services for Windows for Workgroups. ----------------------------------------------------- Additional Information on Setting Up Microsoft Access on a Network Server ----------------------------------------------------- To set up Microsoft Access on a network server, you must run Setup /a from floppy disks. Do not copy the files to a hard disk and run Setup /a from there. Unless you run Setup /a from floppy disks, Microsoft Access 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 /n. If you received Microsoft Access on a compact disc and want to set it up on a network server, you must copy the disk images to floppy disks and run Setup /a from the floppy disks. If you're setting up Microsoft Access on a local machine, you can run Setup directly from the compact disc. -------------------------------------------------------- Version 1.1 Setup and Custom Tool Bars and AccessWizards -------------------------------------------------------- Microsoft Access version 1.1 includes updated UTILITY.MDA and WIZARD.MDA files. If you have modified either of these library databases -- by creating custom tool bars or adding custom AccessWizards, for example -- you should make backup copies of these files before installing Microsoft Access version 1.1. Then modify the version 1.1 copies of the files to include your changes. ----------------------------------------- Running Multiple Data Access Applications ----------------------------------------- Microsoft Access, Microsoft Access custom applications, Microsoft Visual Basic version 3.0, and Visual Basic custom applications all use the same database engine to perform their database-related operations. If one or more of these are running simultaneously, you must be sure that all sections and entries from the initialization (.INI) file that are used for data manipulation (the entries in the [Installable ISAMs], [Paradox ISAM], and [dBASE ISAM] sections) are included in the initialization file for each application. This ensures that you can use data in other formats or applications, such as FoxPro, dBASE, or Paradox. If two or more applications that use the database engine are running simultaneously, the engine is initialized to the .INI file settings of the application that was started first. If the entries in the three data manipulation sections are not included in the .INI file of the first application that starts the database engine, then no application that uses the engine will be able to use FoxPro, dBASE, or Paradox data while the first application is running. For example, when you start Microsoft Access, it initializes the database engine according to the settings in the MSACCESS.INI file. If you then start Visual Basic version 3.0 while Microsoft Access is still running, the database engine will use the MSACCESS.INI file settings rather than the settings in the Visual Basic initialization file. The list below shows where each application looks for its initialization information: Application .INI file ----------- --------- Microsoft Access MSACCESS.INI Microsoft Access application <APPNAME>.INI Visual Basic at design time VB.INI Visual Basic at run time VB.INI Visual Basic .EXE application <APPNAME>.INI ------------------------------------------------------- Using 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 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, see your Network Integration Kit and SQL Server documentation. If you still have questions, contact Microsoft Product Support at one of the numbers listed in the Microsoft Access User's Guide or in Microsoft Access Help. (From the Help menu, choose Contents, and then click Product Support.) ------------------------------------------------------ Using Microsoft Access to Import, Attach, or Export to Microsoft FoxPro Version 2.5 Files ------------------------------------------------------ FoxPro version 2.5 doesn't distinguish between tables created with the MS-DOS version and those created with the Microsoft Windows version. Data in tables created with FoxPro version 2.5 for MS-DOS is stored in OEM format. Data in tables created with FoxPro version 2.5 for Windows is stored in ANSI format. Microsoft Access converts all FoxPro version 2.5 data from an OEM code page to the ANSI 1252 code page when importing or attaching FoxPro 2.5 data, and it converts the ANSI code page to an OEM code page when exporting to FoxPro 2.5 tables. The result is that extended characters in tables created with FoxPro version 2.5 for Windows aren't converted properly. If your FoxPro version 2.5 tables contain extended characters, you should be certain that the tables are stored in OEM format (that is, created by FoxPro version 2.5 for MS-DOS). FoxPro version 2.5a will be able to identify the code page format of the data, enabling Microsoft Access to correctly determine how to convert extended characters. For information on FoxPro version 2.5a, please contact Microsoft End-User Sales at (800) 426-9400. --------------------------------------------- Setting ODBC Options in the MSACCESS.INI File --------------------------------------------- The following table lists all the valid entries applying to ODBC that can appear in the Microsoft Access initialization file, MSACCESS.INI. They appear in the [Debug] and [ODBC] sections. Entry Value Effect ------- ----- ------ Section: [Debug] RmtTrace 0 Use asynchronous query execution if possible; no ODBC API tracing (default). 8 Trace ODBC API calls in ODBCAPI.TXT in the Microsoft Access directory. 16 Force synchronous query execution. 24 Trace ODBC API calls; force asynchronous query execution. Section: [ODBC] TraceSQLMode 0 No tracing of SQL queries (default). 1 Trace SQL queries sent to ODBC in SQLOUT.TXT in the Microsoft Access directory. QueryTimeout S Wait S seconds for queries sent to ODBC, and then stop trying to process the query results (for asynchronous queries only). (Default: 60 seconds). LoginTimeout S Wait S seconds for ODBC login response, and then stop trying to connect to a server. (Default: 20 seconds). ConnectionTimeout S Wait S seconds, and then close idle ODBC connections. (Default: 600 seconds). AsyncRetryInterval M Retry asynchronous queries every M milliseconds. (Default: 500 milliseconds). AttachCaseSensitive 0 Attach the first table whose name matches the specified string, regardless of case. 1 Attach a table only if its name exactly matches the specified string. AttachableObjects string A list of object types you can attach. (Default: 'TABLE','VIEW','SYSTEM TABLE', 'ALIAS', 'SYNONYM'.) SnapshotOnly 0 Get index information when tables are attached so that dynasets are allowed (default). 1 Ignore index information when tables are attached so that only snapshots are allowed. --------------------------------------------------- Installing the ODBC Stored Procedures (INSTCAT.SQL) --------------------------------------------------- Microsoft Access version 1.1 contains a new version of the ODBC stored procedures (found in the INSTCAT.SQL file), which must be installed on a SQL Server before you can access data from that server. However, the INSTCAT.SQL file that comes with version 1.1 can't be used with version 1.0 of Microsoft Access. If you have Microsoft Access version 1.0 and attempt to attach a table from a database on a SQL Server where version 1.1 of the ODBC stored procedures have been installed, you will see this error message: "'<ownername>.<tablename>' isn't a valid name." To fix this problem, you should update all of the computers on your network to version 1.1 of Microsoft Access and install version 1.1 of INSTCAT.SQL on your SQL Servers. If you have Sybase SQL Server databases, you MUST upgrade all users to Microsoft Access 1.1 and use the version 1.1 INSTCAT.SQL, which contains fixes that are required for Sybase SQL Server databases. If you have Microsoft SQL Server databases and have a mixture of Microsoft Access 1.0 and 1.1 installations, you can use the version 1.0 INSTCAT.SQL until all users are upgraded to Microsoft Access version 1.1. The version 1.1 INSTCAT.SQL file is also included with Microsoft Visual Basic version 3.0. If you are using this version of Visual Basic and want to access SQL Server databases from both Visual Basic and Microsoft Access, you should either update all of your users to Microsoft Access version 1.1 or use the version 1.0 INSTCAT.SQL instead of the version supplied with Visual Basic. Visual Basic version 3.0 will work correctly with the version 1.0 INSTCAT.SQL, except that it will be unable to delete indexes from tables. --------------------------------------------- Asynchronous Query Execution and ODBC Drivers --------------------------------------------- When executing queries against Open Database Connectivity (ODBC) data sources, Microsoft Access will attempt, if supported by the ODBC driver, to execute the query asynchronously. The client-server network libraries supported by some ODBC drivers may experience difficulties while executing queries asynchronously. If you encounter problems with query execution, you can disable asynchronous execution by adding the following entry to the [Debug] section of your MSACCESS.INI file: RmtTrace=16 ------------------------------ ORACLE Server and Null Indexes ------------------------------ Some databases, such as ORACLE Server databases, allow multiple Null primary keys in an index, although the index is still considered unique. Microsoft Access can't modify records that have multiple occurrences of the same unique (Null) value, although it can modify other records in the table. If you want to modify records in such a database, make sure that each record has a unique primary key and that no more than one of these is Null. ------------------------------------------------------------ Using Microsoft Access on Novell NetWare Servers and Banyan VINES Servers (Increasing the Number of Record Locks) ------------------------------------------------------------ On Novell NetWare Servers: If you are attempting to use large Microsoft Access databases on a Novell NetWare server, set the "maximum record locks per connection" to the largest allowable value (10,000). The execution of large bulk operations in Microsoft Access (such as a large update query) can cause the server to run out of record lock connections. If you don't set the number of record locks to the maximum value while using Microsoft Access, it could result in the loss of data due to a server crash. See your Novell NetWare documentation for a description of how to set the number of record locks. On Banyan VINES Servers: If you are attempting to use large Microsoft Access databases on a Banyan VINES server, you may exceed the number of record locks allowed. (Note that the number of record locks is not user-definable for Banyan VINES servers.) Banyan VINES version 4.11 allows a maximum of 500 record locks. It is conceivable that a large Microsoft Access bulk operation would require that many record locks. Banyan VINES version 5.00 allows only 100 record locks, which would severely limit Microsoft Access use. Banyan VINES version 5.5 allows at least 10,000 record locks. -------------------------------------------------------- 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 In the Windows Program Manager, choose Run from the File menu. 2 In the Command Line box, type <path> setup /l where <path> is the directory in which the Microsoft Access program files are stored. (Note that l is the letter l, not the number one). For example, if your Microsoft Access files are on drive C in a directory called ACCESS, you'd type c:\access\setup /l in this box. --------------------- Enhancing Performance --------------------- For information on increasing the buffer space, read the PERFORM.TXT file in your Microsoft Access directory. This file also desribes other ways of tuning Microsoft Access to get the best 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. ------------------------- 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 or SVGA monitor only. ---------------------------- 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 the answer to Question 23 in the text file PSSKB.TXT in your Microsoft Access program directory. ------------------------------------------- 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. ------------------------------------------------ Updated SQL Pass Through DLL and Data Definition Language DLL ------------------------------------------------ The SQL Pass Through DLL and Data Definition Language DLL have been updated for Microsoft Access version 1.1. If you are currently using version 1.0 of either of these DLLs (SPT.DLL or MSADDL10.DLL), you must upgrade to the version 1.1 DLLs (MSASP110.DLL and MSADDL11.DLL). You can download the version 1.1 DLLs from the MSACCESS forum on CompuServe. Support for these DLLs is provided on CompuServe only. -------------------- Available Disk Space -------------------- The DBLSPACE utility supplied with MS-DOS version 6.0 (as well as other similar disk compression utilities) enables you to set a compression ratio, which affects the amount of disk space that commands like the MS-DOS command DIR report as available. For example, if you have 5 megabytes of actual disk space, but you've set the compression ratio to 20:1, DIR will report that you have 100 MB of free space. You can use the compression ratio to approximate the amount of room you have for compressed files on your hard disk. However, different kinds of files actually compress at different ratios. For example, the Microsoft Access .EXE file, Help files, and DLLs compress at a ratio closer to 1.5:1. Although DIR may report that you have enough disk space to install Microsoft Access, there might not be enough room to fully install all the Microsoft Access files. If you run out of disk space when installing Microsoft Access, you can free disk space by deleting unnecessary files. You may also want to adjust your compression ratio if you find you are running out of disk space when DIR tells you that you have enough. ----------------------------------------------------- Using DECOMP.EXE to Decompress Microsoft Access Files ----------------------------------------------------- Microsoft Access includes a decompression utility, DECOMP.EXE. You can use DECOMP.EXE to decompress files without running Setup. This allows you to install individual Microsoft Access files. DECOMP.EXE uses the following syntax: DECOMP [/A /F /Q] <source> [<destination>] The <source> argument specifies the file or files to be decompressed; it can be a file name or a wildcard pattern. The <destination> argument is the name of the decompressed file or directory. The following table summarizes the decompression utility command-line options. Option Description ------ ----------- /A Appends the decompressed version of the source file to the file specified by <destination>. /F Forces overwriting of the file specified by <destination>. /Q Calculates the size of the uncompressed file (no output). -------------------------- Outdated Version 1.0 Files -------------------------- The Microsoft Access Setup program for the version 1.1 upgrade installs the version 1.1 files and at the same time deletes or replaces outdated version 1.0 files. The following files are no longer used by Microsoft Access, and are deleted by Setup: BTRVISAM.DLL DBSISAM.DLL MSABC100.DLL MSAES100.DLL MSAIN100.DLL MSAJU100.DLL MSAJT100.DLL PDXISAM.DLL README_.TXT (deleted only if you start Setup by typing setup /a) For a complete list of the version 1.1 files, see the "Microsoft Access Files" section in this README file. ---------------------- Microsoft Access Files ---------------------- File name Destination Description --------- ----------- ----------- 1.wmf N/A Billboard displayed during setup. VGA and higher resolution. 1e.wmf N/A Billboard displayed during setup. EGA resolution. 2.wmf N/A Billboard displayed during setup. VGA and higher resolution. 2e.wmf N/A Billboard displayed during setup. EGA resolution. 3.wmf N/A Billboard displayed during setup. VGA and higher resolution. 3e.wmf N/A Billboard displayed during setup. EGA resolution. 7.wmf N/A Billboard displayed during setup. VGA and higher resolution. 7e.wmf N/A Billboard displayed during setup. EGA resolution. 8.wmf N/A Billboard displayed during setup. VGA and higher resolution. 8e.wmf N/A Billboard displayed during setup. EGA resolution. btrieve.tx$ <Program> Information about configuring Btrieve for use with Microsoft Access. btrv110dl$ <Windows\System> Btrieve ISAM DLL. commdlg.dl_ N/A Uncompressed version of common dialog boxes used by Setup program. ctl3d.dl$ <Windows> 3D-look DLL. decomp.exe N/A Utility to individually decompress files on the Microsoft Access disks. detcmd.dl_ <Program> DLL used by Setup. msa110.hl$ <Program> Microsoft Access version 1.1 Upgrade Help file. msabc110.dl$ <Windows\System> Microsoft Access Basic code DLL. msaccess.ex$ <Program> Microsoft Access executable. msaes110.dl$ <Windows\System> Microsoft Access expression service DLL. msafin.dl$ <Program> Additional financial functions DLL. msain110.dl$ <Program> International resources for Microsoft Access. msajt110.dl$ <Windows\System> Microsoft Access JET engine. msaju110.dl$ <Windows\System> Microsoft Access JET engine utilities. pdx110.dl$ <Windows\System> Paradox version 3.5 ISAM DLL. perform.tx$ <Program> Performance tips. readme.txt <Program> Microsoft Access readme file (this file). Contains issues you should be aware of. setup.exe N/A Setup executable. setup.ini <Program> Setup initialization file. 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 second-level Setup executable. Also used by Change Workgroup utility. stfsetup.in_ N/A Microsoft Access second-level Setup initialization file. wfwdrv.txt N/A Information about Windows for Workgroups driver. wfwnet.dr$ <Windows\System> Windows for Workgroups driver. wizard.md$ <Program> Microsoft Access AccessWizards. workgrp.in_ <Program> Microsoft Access workgroup initialization file used during setup. Renamed STFSETUP.INF. xbs110.dl$ <Windows\System> FoxPro and dBASE ISAM DLL. NOTE: In the Destination column, the name in brackets indicates the most common name for this directory; however, the directory name on your machine may be different. For example, your Windows directory may be called WIN31 or just WIN. The name <Program> indicates the directory where your Microsoft Access program files are stored.