|
|
Posted by Erland Sommarskog on 07/19/05 00:45
(rwyarger@hotmail.com) writes:
> Simon thank you for the quick response. Unfortunately the application
> in question has to use "sa" (there is no way around this).
It sound to me that you had the connection details in a DSN? In such,
isn't it as easy as changing the DSN?
> I will have her run osql.exe and Query Analyser to see if she gets the
> same response. Let me ask you this though - if she is able to get into
> either or both of those methods with the "sa" having a blank password -
> what then would be the reason why a User or System DSN would be still
> having trouble?
I will have to admit that I never fully understood DSNs, and they were
always a hassle. Most applications today do not use DSNs.
One thing to try is a password of one single space.
In any case, I would strongly recommend that you do not have a blank
password for sa.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Navigation:
[Reply to this message]
|