C
chuck rile
When linking to SQL server tables, Ac 2002 forces the
App= argument to be "Microsoft Office XP" & the WSID=
argument to be my windows domain username. I'd like to
use one or the other of them, preferably WSID, to pass
the username from our app, not the windows domain user.
I'm able to do this when establishing an ADO connection
via code AND am able to successfully do it for my pass-
thru queries. However, when I link the tables using the
*exact* same ODBC connect string that works for the pass
thru queries, as soon as the new link is created Access
(I assume Access is the culprit) changes the App= & WSID=
arguments to the values shown above. Has anyone
encountered this and if so do you know how to turn it
off??? Seems like maybe there would be a registry entry
somewhere that would tell Acc to accept the connection
string as presented & not mess w/ it...
App= argument to be "Microsoft Office XP" & the WSID=
argument to be my windows domain username. I'd like to
use one or the other of them, preferably WSID, to pass
the username from our app, not the windows domain user.
I'm able to do this when establishing an ADO connection
via code AND am able to successfully do it for my pass-
thru queries. However, when I link the tables using the
*exact* same ODBC connect string that works for the pass
thru queries, as soon as the new link is created Access
(I assume Access is the culprit) changes the App= & WSID=
arguments to the values shown above. Has anyone
encountered this and if so do you know how to turn it
off??? Seems like maybe there would be a registry entry
somewhere that would tell Acc to accept the connection
string as presented & not mess w/ it...