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

This article was previously published under Q234268
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 55770 (SQLBUG_70)
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).
Specify login and password parameters with .Connect instead of setting them as .Login and .Password.
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 loginWith SQL7.LoginSecure = FALSE.Connect "(local)", "sa", ""Debug.Print .TrueLogin.DisConnectEnd With' Makes trusted connection even though LoginSecure is FALSEWith SQL7        .Name = "(local)"        .LoginSecure = FALSE        .Login = "sa"        .Password = ""        .Connect        Debug.Print .TrueLogin        .DisConnect    End With    Set SQL7 = NothingEnd Sub				

Article ID: 234268 - Last Review: 10/26/2013 08:19:00 - Revision: 5.0

  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft SQL Server 6.5 Standard Edition
  • kbnosurvey kbarchive kbbug kbfix KB234268