ODBC DSNs are stored in the Registry; it should be possible to create a registry file that will include the system DSN settings and than create a script that will merge it into the client's registry hives and push it with a GPO in AD.
Take a look at these keys to get you started:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\[yourdatasource]
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources\[yourdatasource]
Good Luck,
-Erik
"skc" wrote:
> A user creates forms in dBase5.7 and now uses a SQL2000
> database on our network to access tables via dBase.
>
> He has made an application that requires an ODBC DSN
> (System DSN) to be created on the local machine and this
> gets posted to a config file called BDE Configuration
> (part of dBase) and this enables the application to work.
>
> He is now thinking of rolling out this application to
> users on the network - around 30 machines. Instead of
> going round to each machine and adding a System DSN is
> there an easy way to do this from one central source?
> Furthermore, if you look at the footers for System DSN,
> File DSN and User DSN, the File DSN is sharable but not
> compatible with dBase's BDE Config.
>
> So my question is: Is there a Utility to enable System
> DSNs to be hardcoded into clients at the settings pre-
> specified?
>
> He was talking of Group Policy on the Domain Controller -
> do you think this is the way to go about it?
>
> Please help!
>
> skc
>
|
Similar Threads
