Microsoft KB Archive/160075

= FIX: Problems Debugging in Case-sensitive Database =

Article ID: 160075

Article Last Modified on 10/15/2002

-

APPLIES TO


 * Microsoft Visual C++ 4.2 Enterprise Edition

-



This article was previously published under Q160075



SYMPTOMS
If you use a case-sensitive database on Microsoft SQL Server 6.5 and create two stored procedures with the same name but with a different case, you may see inconsistent behavior when you execute or debug one of those procedures.



MORE INFORMATION
To reproduce the problem, create two procedures in a case-sensitive SQL Server 6.5 database: -  CREATE PROCEDURE test AS   DECLARE @a INTEGER DECLARE @A INTEGER select @a = 10 select @A = 20 print 'test done' RETURN -  CREATE PROCEDURE TEST AS   DECLARE @a INTEGER DECLARE @A INTEGER select @a = 1 select @A = 2 print 'TEST done' RETURN When stored procedure names differ only by case (for example, one called test and another called TEST), inconsistent behavior may occur when you execute or debug one of those procedures. For example, when you start debugging 'TEST,' the debugger may show the source code for TEST but it will actually execute 'test'. If you have variables common to both procedures, you will see the values as used in 'test' in the watch window.



STATUS
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This bug was corrected in Visual C++ version 5.0.

Keywords: kbbug kbfix kbsqlprog kbide kbeedition kbvc500fix kbdebug kbprb KB160075

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.