FIX: Host Integration Server ODBC Driver for DB2 Causes Jet Error With Special Characters in Table Names (325068)
The information in this article applies to:
- Microsoft Host Integration Server 2000
This article was previously published under Q325068 SYMPTOMS
When you connect to a host database through Microsoft Access or
Microsoft Excel by using the Host Integration Server ODBC Driver for
DB2, and you use a data source name (DSN) to link tables or to import
tables, you may receive the following error messages:
"The Microsoft Jet database engine could not find the object 'Table Name'. Make sure the object exists and that you
spell its name and path name correctly."
"Can't access table Table Name"
This may occur when the table name contains special characters such as
an underscore (_). For example, a table name such as "aaa_bbb" can
cause this problem.
CAUSE
The jet provider that is used by Excel and Access passes the table name
to the provider as "aaa\_bbb" (for example). The Host Integration
Server ODBC Driver for DB2 incorrectly parses the backslash (\) (or
escape) character.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Host Integration Server 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
328152 How to Obtain the Latest Host Integration Server 2000 Service Pack
The English version of this fix has the file attributes (or later) that
are listed in the following table. The dates and times for these files
are listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference
between UTC and local time, use the Time Zone tab in the Date
and Time tool in Control Panel.
Date Time Version Size File name
---------------------------------------------------------
21-Jun-2002 11:13 5.0.0.866 880,912 Mseidb2d.dll
NOTE: Because of file dependencies, the most recent fix that
contains the preceding files may also contain additional files.
STATUSMicrosoft has confirmed that this is a problem in Host Integration Server 2000. This problem was first corrected in Host Integration Server 2000 Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 3/11/2005 |
---|
Keywords: | kbbug kbfix kbHostIntegServ2000preSP1fix kbHostIntegServ2000SP1fix KB325068 |
---|
|