FIX: SQLColAttribute Returns Incorrect Table Attributes When Table Name Contains a Period (290646)
The information in this article applies to:
- Microsoft SQL Server 7.0
- Microsoft SQL Server 2000 (all editions)
This article was previously published under Q290646
BUG #: 46409 (SHILOH_bug)
BUG #: 56030 (SQLBUG_70)
SYMPTOMS
When you use the SQLColAttribute function to return SQL_DESC_SCHEMA_NAME, SQL_DESC_TABLE_NAME, SQL_DESC_BASE_TABLE_NAME, or SQL_DESC_CATALOG_NAME descriptor information, incorrect values may be returned when the table name contains a period.
CAUSE
ODBC uses periods to delimit SQL Server objects in the format Computer.Database.Owner.Object.
RESOLUTIONSQL Server 2000To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
SQL Server 7.0
To work around this problem, do not use periods within the names of SQL Server objects.
Microsoft Data Access Components (MDAC)To resolve this problem, obtain the latest service pack for Microsoft Data Access Components 2.6. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
300635 INFO: How to Obtain the Latest MDAC 2.6 Service Pack
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. SQL Server 2000 This problem was first corrected in SQL Server 2000 Service Pack 1.Microsoft Data Access Components (MDAC) This problem was first corrected in Microsoft Data Access Components 2.6 Service Pack 1.
Modification Type: | Major | Last Reviewed: | 10/31/2003 |
---|
Keywords: | kbBug kbfix kbMDAC260sp1Fix kbSQLServ2000sp1fix KB290646 |
---|
|