[2005] how to correct the dataset connection string?

[newpat]

My Dataset is generated by adding datasource in vb. All of my table adapter using ConnectionString1 (MySettings)
How can I get this varible and modify its value by my coding?

[wild_bill]

Do you need to change it on the fly, or specify a different connection to your adapter? Say you have loaded ConnectionString1 for your test environment, and ConnectionString2 for your production environment, and you have setup an environment application variable. You could do something like

If My.Settings.Environmnet = "production" Then
    Dim ta As New MyDbTableAdapters.SomeTableAdapter
    ta.Connection.ConnectionString = My.Settings.ConnectionString2
End If

[newpat]

Do you need to change it on the fly, or specify a different connection to your adapter? Say you have loaded ConnectionString1 for your test environment, and ConnectionString2 for your production environment, and you have setup an environment application variable. You could do something like

If My.Settings.Environmnet = "production" Then
    Dim ta As New MyDbTableAdapters.SomeTableAdapter
    ta.Connection.ConnectionString = My.Settings.ConnectionString2
End If

ha, I got a question here. I find my dataset connection in mysetting:
My.Settings.ConnectionString1

But I find that is read only. Is that anyway to change it? Your method can be done, but I have many table adapter..

[wild_bill]

I'm not sure how to do this. We just switched to VS2005 a couple months ago, and all my production applications use our old 1.1 DAL architecture. I am in the same boat when we do switch to exclusivly 2.0. It has always been a pain point for us to migrate between environments. There is talk about skipping a conversion to 2.0, and going straight to 3.5, but I don't know if these issues have been addressed.

[techgnome]

When you add a property to the My namespace, if it is of type ConnectionString, it makes it an Application Level scope setting. All Application-level settings are read only, gawd only knows why. I "get around" this by making it an ordinary string, then setting it to a User-level scope.

that being said, everyplace where you have
ta.Connection.ConnectionString = My.Settings.ConnectionString2

You can replace the use of My.Settings to use a different variable with the connectionstring:
ta.Connection.ConnectionString = mystring_with_connectionstring_init

-tg

[Jenner]

I'm not sure how to do this. We just switched to VS2005 a couple months ago, and all my production applications use our old 1.1 DAL architecture. I am in the same boat when we do switch to exclusivly 2.0. It has always been a pain point for us to migrate between environments. There is talk about skipping a conversion to 2.0, and going straight to 3.5, but I don't know if these issues have been addressed.

There's about 0 conversion between 2.0 and 3.5, so I would if I were you. The BIG difference is from 1.1 to 2.0.

[newpat]

So that..If I have 20 table adapter, I need to run the code 20 times?

If My.Settings.Environmnet = "production" Then
    Dim ta As New MyDbTableAdapters.SomeTableAdapter1
    ta.Connection.ConnectionString = My.Settings.ConnectionString2
End If

If My.Settings.Environmnet = "production" Then
    Dim ta As New MyDbTableAdapters.SomeTableAdapter2
    ta.Connection.ConnectionString = My.Settings.ConnectionString2
End If

That's really a hard task...