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

ID: Q234268


The information in this article applies to:

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 version 6.5 and 7.0.


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 

Additional query words:


Keywords          : kbSQLServ650bug kbSQLServ700bug 
Version           : winnt:6.5,7.0
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: June 22, 1999