Hi

I'm working on a project with multiple developers in VB.NET 2003. SQL
Database

We are mainly connecting to the database by dropping SQL Data Adapter
objects on a form, configuring it and generating a dataset. The Data Adapter
wizard creates a connection object on the form as well. Great.

The problem comes in when one developer has created these objects on a form,
and then another developer goes in a re-runs the Data Adapter wizard (to add
a field to the query for example). The wizard then adds another connection
object to the form because it can't find the existing one (because the
workstation ID is different, because of the different developer). Is there a
better way to do this so we don't have these extra connections being created
when we don't want to? This is creating a lot of hassle.

Thanks

Hi Jim,

I think that solutions can be to make your own datatbase classes or to use a
central SQL server.

You also can make the connection strings in the load events of the forms and
create also a new connection there.

I hope this helps?

Cor

Have you tried removing the WorkStation id parameter from the
connection string?
This parameter will be getting appended to the connectionstring in the
InitializeComponent method of the form for the sql connection. When
the data adaptor is subsequently being re congigured I dont think it
will reinsert the workstation parameter.

Also are you using Integratated database security as opposed to sql
security?