For example, a
SQL Server DSN might include these arguments: ???SQL Server??? ???DSN=Northwind|Server=
(Local)|Description=SQL Server|Database=Northwind||???. In this case, the DSN uses the
SQL Server configuration. The action creates a DSN named Northwind that uses the (Local)
instance of SQL Server and the Northwind database.
CONFIGSYSDSN Name {DSN | Attributes} Creates a new system DSN entry that??™s accessible
by everyone on a particular machine. In all other ways, this action works like the CONFIGDSN
action.
REGSVR Path Registers a new MDAC server on the machine. The path argument specifies the
location of the server DLL. You normally combine this action with the REGMDACVERSION
action to register a new MDAC server.
Creating an ODBC Data Source at the Command Line
More than a few people have experienced problems using the ODBCConf utility because it often
requires use of complex command line syntax. However, there??™s an easier way of adding an ODBC
data source to a remote machine. Simply add the data source using a file DSN. These DSN files
normally appear in the \Program Files\Common Files\ODBC\Data Sources folder of the remote
system.
Pages:
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930