Connecting to SQL Server DB

[John Spiegel]

Hi all,

I'm missing something, probably stupid, on connecting to a SQL Server
database from an aspx file. I haven't really done much w/ SQL Server and
suspect that it's a problem on that side. I've installed the SQL Server
developer edition locally and do have a pubs database.

The connection I'm attempting is the following:

SqlConnection objConnection =
new SqlConnection( "server=localho st;database=pub ;uid=sa;pwd=adm in" );

try
{
// Open the connection.
objConnection.O pen();
/*snip*/
}
catch( Exception ex )
{
ErrorMessage.Te xt = ex.Message.ToSt ring();
}

The exception caught indicates (whether or not 'sa' is the uid I'm trying to
connect with):
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server
connection. (w/Windows-only Authentication) or
Login failed for user 'sa'. (Windows and SQL Server Authentication)

I have been able to create a connection through VFP (though using ODBC).
The connection string it creates is:
DSN=SQLServer1; UID=sa;PWD=admi n;APP=Microsoft Visual FoxPro;WSID=J2K , which
indicates to me that the sa/admin login is correct (which is what Iset at
installation).

Any ideas?

TIA,

John

[Aaron Bertrand - MVP]

I don't mind cross-posting so much as multi-posting. However this probably
belonged in one of the following sets:

[microsoft.publi c.dotnet.framew ork.adonet,
microsoft.publi c.sqlserver.con nect]

[microsoft.publi c.dotnet.framew ork.adonet,
microsoft.publi c.sqlserver.con nect]

[microsoft.publi c.sqlserver.con nect]

--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/


"John Spiegel" <js******@YETAN OTHERSPAMHATERc-comld.com> wrote in message
news:#R******** ******@TK2MSFTN GP09.phx.gbl...

Hey Eric,

Aside from the connection issue...

Cross-posting is bad.
I've seen this dozens of times (part of why 90+% of the time I don't do

it). But I've never really understood what the problem is--particularly in a case where there are multiple technologies thrown in the mix. Is it a resource
issue for the newserver or confusion/clutter issue for the readers? Just
trying to understand.

Sorry for being bad,

John

[Eric Sabine]

You know you're right. It wasn't _that_ bad. Perhaps I just jumped on
something I don't like to see. One of the problems with x-posting is
readers who perhaps are not subscribed to the other groups might not see all
of replies. Likewise, when you are searching on a problem, you might
believe you're seeing incomplete threads hence a solution to an issue was
never found, however the thread could have just continued elsewhere.

Eric
"John Spiegel" <js******@YETAN OTHERSPAMHATERc-comld.com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

Hey Eric,

Aside from the connection issue...

Cross-posting is bad.
I've seen this dozens of times (part of why 90+% of the time I don't do

it). But I've never really understood what the problem is--particularly in a case where there are multiple technologies thrown in the mix. Is it a resource
issue for the newserver or confusion/clutter issue for the readers? Just
trying to understand.

Sorry for being bad,

John

[Aaron Bertrand - MVP]

> something I don't like to see. One of the problems with x-posting is

readers who perhaps are not subscribed to the other groups might not see all of replies.

I bet this is rare. Usually, cross-posted groups are dropped when a user
finds that one or more of the groups was off-topic. So, a user who
frequents the off-topic group but not the on-topic group, would be unlikely
to be interested in the thread if it went solely to off-topic groups they
don't subscribe to.

--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

[John Spiegel]

My thanks and apologies to all. In a "didn't see the forest through the
trees" kind of way, I eventually realized that the downloaded code I was
using was using the compiled version of codebehind file and not the
on-the-fly changes I was making in the .cs file. Sheesh!

Thanks again for getting involved (and I learned some stuff in the process!)

- John

"John Spiegel" <js******@YETAN OTHERSPAMHATERc-comld.com> wrote in message
news:eX******** *****@TK2MSFTNG P11.phx.gbl...

Hi all,

I'm missing something, probably stupid, on connecting to a SQL Server
database from an aspx file. I haven't really done much w/ SQL Server and
suspect that it's a problem on that side. I've installed the SQL Server
developer edition locally and do have a pubs database.

The connection I'm attempting is the following:

SqlConnection objConnection =
new SqlConnection( "server=localho st;database=pub ;uid=sa;pwd=adm in" );
try
{
// Open the connection.
objConnection.O pen();
/*snip*/
}
catch( Exception ex )
{
ErrorMessage.Te xt = ex.Message.ToSt ring();
}

The exception caught indicates (whether or not 'sa' is the uid I'm trying to connect with):
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection. (w/Windows-only Authentication) or
Login failed for user 'sa'. (Windows and SQL Server Authentication)

I have been able to create a connection through VFP (though using ODBC).
The connection string it creates is:
DSN=SQLServer1; UID=sa;PWD=admi n;APP=Microsoft Visual FoxPro;WSID=J2K , which indicates to me that the sa/admin login is correct (which is what Iset at
installation).

Any ideas?

TIA,

John

[len nelson]

It's true, the sqlConnection does not allow you to use an ODBC
connection so you'd either have to not use one, use the slower, less
optimized odbcConnection, OR... just read the ODBC settings from the
registry yourself. This is safe because if you're using a sqlConnection
then you're already commited to using just SQL server and so the
registry format should not change. Here's some sample code form
creating my connect string....

public DataConnection (string strUserName, string strPassword, string
strDSN)
{
Microsoft.Win32 .RegistryKey key =
Microsoft.Win32 .Registry.Local Machine.OpenSub Key("SOFTWARE\\ ODBC\\ODBC.I
NI\\" + strDSN);
if (key == null)
{
throw new Exception ("The specified ODBC datasource does not
exist.");
}
string databaseName = (string)key.Get Value ("Database") ;
string server = (string)key.Get Value ("Server");

m_strConnect = "user id=" + strUserName + ";password= " + strPassword
+ ";initial catalog=" + databaseName + ";data source=" + server;
}

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!