problem using one connection string per application

hi guys I incountered the same problem and i would like to share my solution with you hoping it would be some help i created a class "ConnString" and included in it a public method that returns a string as follows: public class ConnString { public ConnString() { // // TODO: Add constructor logic here // } public string GetConnString() { return "Data Source=HRSRV;Initial Catalog=Dies;Integrated Security=SSPI"; } } and after that when ever i need to creat a connection i do the following ConnString objConnString = new ConnString(); SqlConnection conn = new SqlConnection(objConnString.GetConnString()); this way if anychange happens to the connection string i change it only once from the "ConnString()" class and i am done i hope this helps take care guys

I think it would be easy to create a public property in the main form that wraps the connection on that form. For each of the other forms, just create an identical property, but remove the auto-created connection from the designer on each of the other forms. That way only the main form actually has a connection object. The rest have a connection PROPERTY. When you create an instance of any of the child forms, just set the connection property, too. Now you only have to modify one connection at runtime or design-time and all forms will see it. To avoid changing a lot of existing code, just make the property name the same as the connection name was. Then the code is left unbroken.

you could set the sqlConnection's connection string to a global string variable, or create a single SQLConnection, and have the dataAdapters use it as the connection. The wizard is what created all the extra connections, and it will be some work for you to consolidate them into one.