Description of the ODBC.INI File

Last reviewed: February 5, 1998
Article ID: Q106370
The information in this article applies to:
  • Microsoft Word for Windows, version 6.0

SUMMARY

This article describes the contents of the open database connectivity (ODBC) initialization file, ODBC.INI. The ODBC.INI file is installed with a complete installation of Word 6.0 for Windows.

NOTE: Microsoft does not recommend direct modification of the ODBC.INI file with a text editor. The preferred method for editing the ODBC.INI file is to use either the ODBC Setup program or the ODBC administration tool.

You can access the ODBC Setup program during Word for Windows installation. You can access the administration tool by choosing the ODBC icon in Windows Control Panel.

MORE INFORMATION

The ODBC Data Sources Section

This section lists the data sources installed during Word 6.0 for Windows setup, or as specified by the user. Each entry lists a data source and the description of the driver it uses. The driver description is usually the name of the associated DBMS (Database Management System). The format of the section is:

   data-source-name=driver-description

For instance, the following example includes the data sources installed by Word and a user-defined source named "My Address List." "My Address List" uses a Microsoft Access DBMS.

   [ODBC Data Sources]
   MS Access Databases=Access Data (*.mdb)
   FoxPro Files=FoxPro Files (*.dbf)
   dBase Files=dBase Files (*.dbf)
   Paradox Files=Paradox Files (*.db )
   My Address List=Access Data (*.mdb)

The Data Source Specification Sections

Each data source listed in the [ODBC Data Sources] section has a section of its own in the ODBC.INI file. The section name is the data source name from the [ODBC Data Sources] section above. It will list the driver DLL and a description of the data source. This section will also list other information such as translation DLLs if the driver supports them, and other information specific to the driver. The general format appears as:

   [data-source-name]
   driver=driver-DLL-path
   description=data-source-description
   optional-entries=optional-strings

For instance, the following example contains the data source specifications for two of the data sources listed in the [ODBC Data Sources] section above:

   [FoxPro Files]
   Driver=C:\WINDOWS\SYSTEM\SIMBA.DLL
   FileType=FoxPro 2.5
   SingleUser=False

   [My Address List]
   Driver=C:\WINDOWS\SYSTEM\SIMBA.DLL
   Description=A List of Friends, Relatives and Business Contacts
   FileType=RedISAM
   DataDirectory=c:\access\list.mdb
   SingleUser=False
   UseSystemDB=False

Default Data Source Specification Section

Optionally the ODBC.INI file may contain a default data source specification section. The data source must be named "Default" and is not listed in the [ODBC Data Sources] section. The format of the default data source specification section is the same as any other data source specification section:

   [Default]
   driver=driver-DLL-path
   description=data-source-description
   optional-entries=optional-strings

REFERENCES

"Microsoft Word Developer's Kit," Appendix B, "ODBC Extensions for Microsoft Word," "Setting Up Data Sources" section (page 906)


KBCategory:
KBSubcategory: kbmerge
Additional query words: 6.0 access winword word6
Keywords : kbmerge kbprint
Version : 6.0
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 5, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.