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 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
Also are you using Integratated database security as opposed to sql
security?
"Jim Dafnis" <skia...@hotmail.com> wrote in message news:<ejIG07$8DHA...@TK2MSFTNGP10.phx.gbl>...
Funny....you can't stand the site of weirdos as you repeated incesantly over the years, but there's a weirdo in front of your very own mirror every day with a large head & fat face to boot! I guess since you focus on others all the time you DON'T focus on fixing YOUR own retardedness huh?
From http://www.google.ca/search?q=jim+dafnis&hl=en&sa=2
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com/g/