#3 - Select Type of DSN to Create
default setting is to create a system DSN, the one most commonly used in my
experience. Both system and user DSN's are registry based, while a File DSN is
stored in the file system. Take a look at my article DSN's -
What are they? for details about how
DSN's work and the differences between them.
#4 - Options
are two options here. The first is 'ServerName as Prefix'. Check this to give
your DSN's more descriptive names. If the server name is SQLTest and the
database name is Pubs, checking this box will create a DSN called SQLTest_Pubs.
This is very handy if you have databases on different servers with the same
names. It also makes picking the DSN easier later on as all the DSN's from each
server will be grouped together.
The second option, 'Trusted Connection', is checked by default and indicates
that the DSN will use NT security to connect. Uncheck this box if your users (or
your application) uses SQL logins.
#5 - Generate the DSN's!
you selected System or User as the DSN type, a file called DSN.REG will be
created in the folder where DSNGen.exe is installed. It is NOT entered into the
registry yet. If you chose to create a File DSN, then you will one *.DSN file
per database in the DSNGen folder. Again, these are not copied to your default
File DSN folder at this time. This allows you to review them before deploying,
reducing concerns about changes made to your machine. Another good read for this
is that in many cases you may be creating them on your machine for use n a
#6 - Deploy the DSN's
you don't want to deploy the DSN's on your machine, just click
'I'll Deploy the DSN's Later'. You can then review the files before deploying.
you selected System or User as the DSN type, clicking on 'Deploy DSN's Now' will use RegEdit to merge the
DSN.REG file into the registry. If you created
file DSN's, they will be copied to your system DSN folder (which is usually C:\Program Files\Common Files\ODBC\Data Sources).
to DSNGen Introduction Proceed
to Download Page