tobin46
asked on
SQL Connection and DataAdapters
When developing a VB.net application with SQL Server 2000, I'm developing the app on a development computer. The app is going to be installed on another computer.
When I create the data adapters and SQL Connection, they point to the local database. What happens when I install this on the intended PC? Is this going to be a problem?
If this is going to be a problem, how can I address this now before I get too far into development?
Thanks!
When I create the data adapters and SQL Connection, they point to the local database. What happens when I install this on the intended PC? Is this going to be a problem?
If this is going to be a problem, how can I address this now before I get too far into development?
Thanks!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This is what I did some years ago:
instead of hadcoding the sql server name, I made it read it from the registry.
I made another application called "Application Admin" to set the server name in the registry.
instead of hadcoding the sql server name, I made it read it from the registry.
I made another application called "Application Admin" to set the server name in the registry.
http://connectionstrings.com/?carrier=sqlserver
for a list of connection strings.