Win 7 Filtering out Password?
We recently have ported our GIS system to a Win 7 box in preperation of converting our whole system and ran into problem accessing a side database (SQL 2000) on one of the applications. The prolem is here:
(ADODB.Connection)_pxApp.Connection).ConnectionString;
Usually this passes us the connection string that was used to log into the aplication with the users credintials imbeded in it. But with Win 7, I get this:
Provider=SQLOLEDB.1;User ID=rona;Initial Catalog=process;Data Source=pudoagis1;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=N10L128;Use Encryption for Data=False;Tag with column collation when possible=False;
Note that I HAVE NOT taken the password=XXXXX out of this connection string, it seems like Win 7 is 'helping' me by doing that. If I hard code the connection string in with a valid password it works fine.
Has anyone heard of this? Is this a setting in Win 7 I need to look at?
(ADODB.Connection)_pxApp.Connection).ConnectionString;
Usually this passes us the connection string that was used to log into the aplication with the users credintials imbeded in it. But with Win 7, I get this:
Provider=SQLOLEDB.1;User ID=rona;Initial Catalog=process;Data Source=pudoagis1;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=N10L128;Use Encryption for Data=False;Tag with column collation when possible=False;
Note that I HAVE NOT taken the password=XXXXX out of this connection string, it seems like Win 7 is 'helping' me by doing that. If I hard code the connection string in with a valid password it works fine.
Has anyone heard of this? Is this a setting in Win 7 I need to look at?
Selected Articles