J
Jim Dafnis
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
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