Re: SetNet32 information updated when using connection string.
- From: "Art S. Kagel" <art.kagel@xxxxxxxxx>
- Date: Thu, 30 Aug 2007 22:24:41 -0000
On Aug 30, 10:54 am, hometoast <hometo...@xxxxxxxxx> wrote:
If I specify an IP address in my connection string, after the
connection is made setnet32 has been changed to use that hostname
instead of the default.
Is this is what's intended?
Our environment is such our production and test servers have the same
name, but are on different machines. This lets the development staff
use one hosts file and the production users use another. I'm writing
an app which attempts to compare database tables for verification
between the test and production environments. So I would want to
connect to servern...@xxxxxxxx and servern...@xxxxxxxx at the same
time; but this seems impossible.
Is there a way to NOT update the registry/setnet as a sideeffect of
connecting with an alternate hostname?
That's the first mistake. You should NEVER have two server instances
with the same name on different machines. Environment variables, ODBC
tags, and other mechanisms were developed for allowing your
applications to know have to know the server''s name at compile time
but to either determine the servername at runtime or to just connect
to a default server. Fix that and things get easier. I think that
you are the third person this month to have a similar problem with the
same cause.
Art S. Kagel
.
- Follow-Ups:
- Re: SetNet32 information updated when using connection string.
- From: hometoast
- Re: SetNet32 information updated when using connection string.
- References:
- SetNet32 information updated when using connection string.
- From: hometoast
- SetNet32 information updated when using connection string.
- Prev by Date: Re: Nasty IDS 10.00.UC6 bug
- Next by Date: Partition dilemma
- Previous by thread: SetNet32 information updated when using connection string.
- Next by thread: Re: SetNet32 information updated when using connection string.
- Index(es):
Relevant Pages
|
Loading
