Mitch,
This is what I was thinking of doing in my current project.  There's one 
thing I don't understand - how do you pick up the new username/password of 
the server?  Sorry if I'm being dim, but I don't see how to connect to the 
server if the user/password in the client app is wrong.


> The way I get around the compile problem is to put the connectionstring 
into the registry.
> The username and password is encoded and the app runs each through an
> algorithm before using it. This allows me to change the 
username/password 
> on the server and the next time the client connects it detects a change 
> and updates the registry with the new login information. After a week
> or so I can remove the old username/password...
> 
> This works pretty slick for us.
> 
> 
> Mitch Spruill
> Mannatec, Inc.
> 
> 
> -----Original Message-----
> From: dburr [mailto:dburr@n...]
> Sent: Tuesday, August 14, 2001 07:04 PM
> To: professional vb
> Subject: [pro_vb] RE: please don't laugh, I'm new here
> 
> 
> 1.) we were all new at one point in time so no one is going to laugh at 
you
> 
> 2.) Yes it is very simple, you can either use a connection string with or
> without a DSN to connect to any MSSQL database across any TCP/IP network
>  public internet included ).
> 
> There are pros and cons to both. The DSN allows you to easily change the
> connection separte from the client app, but can expose connection details
> you may not want exposed. If you embed the connection string in the app 
then
> you need to either re-compile the app or keep it separate in a DLL then
> redistribute the DLL if the connection changes ( never exposes the
> connnection information ).
> 
> If you want to use the connection string it is in the following format:
> 
> strConnString = "Provider=SQLOLEDB; " _
> 		  & "Initial Catalog=AAAAA; " _
> 	        & "Data source=BBBBB;" _
> 	        & "Network Address=CCCCC;" _
> 		  & "UID=DDDDD;PWD=EEEEE"
> 
> 
> AAAAA To EEEEE represent values. Replace these with un-quoted values as
> follows:
> 
> AAAAA = name of the database
> BBBBB = name of the MSSQL server ( normally the same as the machine name 
it
> resides on )
> CCCCC = IP Address of the MSSQL server machine
> DDDDD = User name to use when connecting to the SQL datasource
> EEEEE = the password for the username in DDDDD
> 
> Hope this helps
> 
> 
> 
> 
> Thank You
> Donald Burr
> C.I.O.
> Nationwide Auction Systems
> City of Industry, California
> Voice:  (xxx) xxx-xxxx  Ext. 248
> Fax:  (xxx) xxx-xxxx
> Cel:  (xxx) xxx-xxxx
> E-Mail: dburr@n... <mailto:dburr@n...>
> 
> 
> 
> -----Original Message-----
> From: olivier tardif [mailto:otardif@n...]
> Sent: Friday, August 10, 2001 9:55 PM
> To: professional vb
> Subject: [pro_vb] please don't laugh, I'm new here
> 
> 
> Here goes for the Naive Question Of The Day:
> 
> Is there a way, any way, to have a client application connect to a mssql
> database server which IS NOT on the same domain and WITHOUT the client 
app
> being a web application? In other terms: is it possible to open a 
database
> connection to a server in a different domain using only its IP address 
and
> its connection string, and without using technologies such as ASP, PHP,
> etc.?
> 
> thanks
> - olivier