No settings on the servers have changed. (Checked with the admin). I did find something about SQL Server 2000 access requiring full trust for debugging. Tried turning the SQL Server debugging off to no effect.

At this point, I'm starting over. This is a test/learn project anyway. Thanks for all your help. I'll be back more than likely with other questions. (Hopefully not this one)

Richard



>Richard,
>
>I haven't used ClickOnce, so I don't know if that has anything to do with your problem.
>
>I'm guessing that something having to do with permissions has probably changed on the server ... either the shared file server or SQL Server.
>
>~~Bonnie
>
>
>>The sql server is elsewhere. The project itself is on a shared file server.
>>
>>I'm still very new at this. To learn I might restart from scratch (again) and pay closer attention to the security stuff. How much does it mean if I don't check ClickOnce-Full trust? ANY suggestions on this would be appreciated.
>>
>>Thanks
>>
>>Richard
>>
>>>Hmmm ... where is the server you're trying to access? Is it on your PC or elsewhere?
>>>
>>>~~Bonnie
>>>
>>>
>>>
>>>>Actually, I haven't touched it for a month which means NOTHING changed. (Unless someone else did and didn't tell me) I was about to start back on it and was simply running it to see where I had left off. In that time, Microsoft put out a security patch for .NET 2.0 which was downloaded and installed. Could that be the change?
>>>>
>>>>APP_CONNECTIONSTRING = "Persist Security Info=True;Initial Catalog=CBCManage;"
>>>>
>>>>In case it matters, this is SQL Server 2000.
>>>>
>>>>
>>>>
>>>>
>>>>>OK, so if it was working a month ago, something must have changed ... any idea what might have changed between now and a month ago? What's in CBCManager.Properties.Resources.APP_CONNECTIONSTRING?
>>>>>
>>>>>~~Bonnie
>>>>>
>>>>>
>>>>>
>>>>>>This is a Windows Forms application.
>>>>>>
>>>>>>Okay, I'm at a loss over this error:
>>>>>>
>>>>>>Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
>>>>>>
>>>>>>This is the code it says is causing the problem:
>>>>>>
>>>>>>frmLogin is simply a login form. Line with -> is the line with the error.
>>>>>>

>>>>>>oSQLConnection.ConnectionString =
>>>>>>	CBCManager.Properties.Resources.APP_CONNECTIONSTRING +
>>>>>>	"Data Source=" + frmLogin.ServerName.Trim() +
>>>>>>	";User ID=" + frmLogin.UserName.Trim() +
>>>>>>	";Password=" + frmLogin.Password;
>>>>>>
>>>>>>	try
>>>>>>	{
>>>>>>	oSQLConnection.Open();	//Attempt the connection
>>>>>>	}
>>>>>>
>>>>>>	catch(SqlException oException)	// Fails-need to know why
>>>>>>	{
>>>>>>	     switch(oException.Number)
>>>>>>	     {
>>>>>>		// Invalid password/username
>>>>>>		case 18456:
>>>>>>		MessageBox.Show("Invalid User ID or password.");
>>>>>>		break;
>>>>>>
>>>>>>		default:
>>>>>>		{
>>>>>>		MessageBox.Show(this.ShowSQLError(oException));
>>>>>>		break;
>>>>>>	        }
>>>>>>	     }
>>>>>>	     blnLoginError = true;	// Some error doesn't matter what
>>>>>>	}
>>>>>>
>>>>>>	catch
>>>>>>	{
>>>>>>->	     throw;
>>>>>>	}
>>>>>>
>>>>>>	finally	// we want to insure it loops back to the
>>>>>>        {
>>>>>>	blnLoginSuccess = !blnLoginError;
>>>>>>	}
>>>>>>

>>>>>>
>>>>>>This was working just a month ago, now I'm getting this error. What causes things like this and how do I get rid of them? I did not use the ClickOnce thing. Do I need to?
>>>>>>
>>>>>>When I first tried a test app with .NET, I got a similar error. I rebuilt it from scratch without using ClickOnce to get rid of it. I've gotten too far on this to go back to the drawing board.
>>>>>>
>>>>>>Richard