FIX: You receive a "can't analyze" error message when you generate objects if a field name contains Japanese double-byte symbol characters in Visual Studio .NET 2002 (332180)
The information in this article applies to:
- Microsoft Visual Studio .NET (2002), Professional Edition
- Microsoft Visual Studio .NET (2002), Enterprise Architect Edition
- Microsoft Visual Studio .NET (2002), Enterprise Developer Edition
- Microsoft Visual Studio .NET (2002), Academic Edition
This article was previously published under Q332180 SYMPTOMS When you use the Data Configuration Wizard to generate a sqlDataAdapter object or an oleDbDataAdapter object, you receive a "can't analyze" error message at each of
the following two lines if any field name contains Japanese double-byte symbol
characters such as a parenthesis ("(" or ")"), and the field permits a NULL
value: Generate Update statement
Generate Delete Statement CAUSE This problem occurs because Microsoft SQL Server cannot
declare names of parameters by using Japanese double-byte symbol
characters.RESOLUTIONService pack information
To resolve this problem, obtain the latest service pack for Micorsoft Visual
Studio .NET. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
837234 List of bugs that are fixed in Visual Studio .NET 2002 Service Pack 1
Hotfix information
The English version of this hotfix has the file attributes (or later file attributes) 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 Platform
-------------------------------------------------------------------------------
17-Oct-2002 1:53:57 7.0.9619.0 3,607,104 Microsoft.vsdesigner.dll i386 STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Visual Studio .NET 2002 Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 9/27/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbvs2002sp1sweep kbvs2002sp1fix kbVSNetPreSP1fix kbbug kbfix kbQFE KB332180 kbAudDeveloper |
---|
|