Are you currently using System DSN or File DSN in your current
configuration? If you are using file DSN, you can just edit the one of
the FILE DSN's, upload it to a server, and propagate the file to all of
the client computers in the current FILE DSN directory using a logon
script. Make sure you keep the name of the file the same. The default
FILE DSN directory should be c:\program files\common files\ODBC\Data
Sources
If you are using SYSTEM DSN, then the DSN entry is in the registry. You
can propagate the reg entry using a logon script as well. The Reg branch
where the info is located is
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\(WHATEVER_THE_NAME_OF_THE_DSN_
ENTRY). Make sure you use the same name for the DSN entry as your
previous one.
-----Original Message-----
From: Blackburn Barrett [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 20, 2001 11:24 AM
To: NT System Admin Issues
Subject: ODBC Connections
All,
Is there as Reg Hack/Utility that will allow me to add a system DSN
without
having to go to 175 machines and add it to each one? It is a NT4.0 sp6a
environment with Office 2k sr1. We are moving from an access oriented
back
end to a SQL7 back end, and I would prefer not to have to go to each
individual machine to add the connectivity.
TIA for your help.
Barrett Blackburn
___________________________________
Things a Mother Learns: No matter how much Jell-O you put in a swimming
pool, you still can't walk on water.
___________________________________
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
