"B. Chernick" <BChernick@discussions.microsoft.com> wrote in message =
news:7A251269-4947-4FEA-A596-CC0043BC6A37@microsoft.com...
>I feel like I'm forgetting something. Assume Visual Studio 2005 (VB) =
and=20
> assume you have created a data source and dataset by the usual means. =
=20
> Assume multiple tables. =20
>=20
> Now you have a designer.vb module associated with the dataset =
containing an=20
> InitConnection sub for each table, as well as an ominous message at =
the top=20
> of the file warning against manual change. (For simplicity's sake =
also=20
> assume that you chose the option not to create an Application Setting=20
> connection string.)=20
>=20
> Given this, is there any one place in the dataset I could =
programmatically=20
> set the connection string, or must I always do it for each individual =

"William (Bill) Vaughn" wrote:

> I would leverage the settings value created by the Data Source config wizard.
>
> Dim cn As New SqlClient.SqlConnection
>
> cn.ConnectionString = My.Settings.CustomerConnectionString
>
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> -----------------------------------------------------------------------------------------------------------------------
>
> "B. Chernick" <BChernick@discussions.microsoft.com> wrote in message news:7A251269-4947-4FEA-A596-CC0043BC6A37@microsoft.com...
> >I feel like I'm forgetting something. Assume Visual Studio 2005 (VB) and
> > assume you have created a data source and dataset by the usual means.
> > Assume multiple tables.
> >
> > Now you have a designer.vb module associated with the dataset containing an
> > InitConnection sub for each table, as well as an ominous message at the top
> > of the file warning against manual change. (For simplicity's sake also
> > assume that you chose the option not to create an Application Setting
> > connection string.)
> >
> > Given this, is there any one place in the dataset I could programmatically
> > set the connection string, or must I always do it for each individual table