ODBC Files Installed to User Directory with Shared Windows
ID: Q117717
|
The information in this article applies to:
-
Microsoft Office for Windows 95, version 7.0
-
Microsoft Office for Windows, versions 4.0, 4.2, 4.2c, 4.3, 4.3c
-
Microsoft Word for Windows, versions 6.0, 6.0a
-
Microsoft Excel for Windows, version 5.0
SYMPTOMS
When you run a workstation installation of one of the above applications on
a computer running Microsoft Windows from a server, the Open Database
Connectivity (ODBC) files are installed to your personal Windows directory,
even if the Server option was selected as the location for shared
applications during the administrative installation.
CAUSE
This behavior is caused by the way the ODBC files are installed. The ODBC
driver files are always installed to your user directory when you run a
workstation installation and are running Microsoft Windows from a server.
WORKAROUND
To prevent the ODBC files from being installed in your personal Windows
directory, you can edit the SETUP.STF file. Note that if you make these
changes to the SETUP.STF file, ODBC functionality is NOT installed and is
not available on the workstation.
NOTE: Each application that uses ODBC installs the ODBC files if they are
not already on your computer. Therefore, to prevent installation of these
files, you must edit the SETUP.STF file for each application you install
that uses ODBC. For example, if you modify the SETUP.STF file for Microsoft
Word for Windows and then perform a workstation installation of Microsoft
Excel for Windows, the ODBC files are installed.
WARNING: This modification is not supported by Microsoft Product Support
Services (PSS). Although PSS will support some modifications to a BACKUP
copy of the SETUP.STF file and will help customers modify specific lines of
an STF, we will not rewrite the entire file in order to achieve a desired
configuration. As a general rule, support is limited to options that can
normally be changed by a user during a standard installation of the
application.
Steps to Edit SETUP.STF
- Make a backup copy of your SETUP.STF file.
- Open SETUP.STF in Microsoft Excel (or another suitable text editor).
NOTE: If you open SETUP.STF in Microsoft Excel 5.0, complete the
following additional steps before continuing:
- In the Text Import Wizard dialog box, choose Next until Step 3
Of 3 appears.
- In the Text Import Wizard - Step 3 Of 3 dialog box, under Data
Preview, click the second column to select it. Under Column Data
Format, select the Text option, and choose Finish.
- Make the changes outlined below (that is, find each object ID listed in
the Object ID column and change the corresponding "Install During Batch
Mode" entry in the .STF file to match the value in the appropriate table
below). If the entry in the table is "(blank)," clear whatever text is
in the cell and leave it blank.
NOTES:
- If the Object ID and Title values in your .STF file do not correspond as
in the appropriate table below, use the Title column as your reference
for changing the "Install During Batch Mode" value.
- The modifications to the Microsoft Office SETUP.STF file include changes
to work around a problem running a quiet-mode installation in which
Setup can install only Microsoft Excel 5.0 and its components. For more
information about this problem, query on the following words in the
Microsoft Knowledge Base:
quiet and mode and components and excel
Microsoft Office Version 4.2:
Object ID Install During Batch Mode Title
(Column A) (Column B) (Column C)
---------------------------------------------------------
33 no &Typical
36 yes &Workstation
57 no Data Access
91 (blank) XL5Workstation_shared
96 no Data Access
108 no Data Access
1608 no Microsoft PowerPoint
1609 no Microsoft PowerPoint
1610 no Microsoft PowerPoint
1611 yes Microsoft PowerPoint
1618 yes PPWorkstation_Local_Files1
1619 (blank) PPWorkstation_Local_Files2
1620 yes PPWorkstation_Local_Files3
1621 (blank) PPWorkstation_Local_Files4
3209 no Microsoft Word
3210 no Microsoft Word
3211 no Microsoft Word
3212 yes Microsoft Word
3267 no Data Access (ODBC)
4262 yes Workstation
Microsoft Office Version 4.3:
Object ID Install During Batch Mode Title
(Column A) (Column B) (Column C)
---------------------------------------------------------
62 no Data Access
96 (blank) XL5Workstation_shared
101 no Data Access
113 no Data Access
1589 no Microsoft PowerPoint
1590 no Microsoft PowerPoint
1591 no Microsoft PowerPoint
1592 yes Microsoft PowerPoint
1599 yes PPWorkstation_Local_Files1
1600 (blank) PPWorkstation_Local_Files2
1601 yes PPWorkstation_Local_Files3
1602 (blank) PPWorkstation_Local_Files4
3157 no Microsoft Word
3158 no Microsoft Word
3159 no Microsoft Word
3160 yes Microsoft Word
3215 no Data Access (ODBC)
4184 yes Workstation
4249 no Microsoft Access
4250 no Microsoft Access
4251 no Microsoft Access
4252 yes Microsoft Access
Microsoft Word Version 6.0a:
Object ID Install During Batch Mode Title
(Column A) (Column B) (Column C)
-----------------------------------------------------------
76 no Data Access (ODBC)
Microsoft Excel Version 5.0:
Object ID Install During Batch Mode Title
(Column A) (Column B) (Column C)
-----------------------------------------------------------
22 no Data Access
34 no Data Access
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article. We are researching this problem
and will post new information here in the Microsoft Knowledge Base as it
becomes available.
MORE INFORMATION
The following is a list of the ODBC files (approximately 2 megabytes) that
are installed to your personal Windows directory:
DRVACCSS.HLP
DRVDBASE.HLP
DRVFOX.HLP
DRVPARDX.HLP
DRVSSRVR.HLP
MSJETDSP.DLL
ODBC.DLL
ODBCADM.EXE
ODBCINST.DLL
ODBCINST.HLP
ODBC.INI
ODBCINST.INI
ODBCISAM.INI
PDX110.DLL
RED110.DLL
SIMADMIN.DLL
SIMBA.DLL
SQLSVR.DLL
XBS110.DLL
For more information about extra system files being installed to your
Windows directory, see the following article in the Microsoft Knowledge
Base:
Q115594 Office: Extra Files in User Directory with Shared Windows
Additional query words:
1.00 2.00 6.00a kbsetup acme
Keywords :
Version : WINDOWS:4.0,4.2,4.2c,4.3,4.3c,5.0,6.0,6.0a; Win95:7.0
Platform : Win95 WINDOWS
Issue type :