Microsoft KB Archive/234268

= FIX: SQLDMO - .Login and .Password Properties are Ignored with .LoginSecure = FALSE =

Article ID: 234268

Article Last Modified on 3/14/2006

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition
 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q234268



BUG #: 55770 (SQLBUG_70)



SYMPTOMS
In a SQL Distributed Management Objects (DMO) program with .LoginSecure set to FALSE, the .Login and .Password properties are ignored and a trusted connection is made.

If login and password parameters are given with the .Connect, a standard connection is made when .LoginSecure is set to FALSE (as expected).



WORKAROUND
Specify login and password parameters with .Connect instead of setting them as .Login and .Password.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

For more information, contact your primary support provider.



MORE INFORMATION
Here is sample code that demonstrates the problem and the workaround: Private Sub Form_Load

Set SQL7 = CreateObject("SQLDMO.SQLServer")

' Performs standard login

With SQL7 .LoginSecure = FALSE .Connect "(local)", "sa", "" Debug.Print .TrueLogin .DisConnect

End With

' Makes trusted connection even though LoginSecure is FALSE

With SQL7

.Name = "(local)" .LoginSecure = FALSE .Login = "sa" .Password = "" .Connect Debug.Print .TrueLogin .DisConnect

End With

Set SQL7 = Nothing

End Sub

Keywords: kbbug kbfix KB234268

-

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

© Microsoft Corporation. All rights reserved.