The Connection Object, ODBC and DSN

This script doesn't do anything except illustrating the connection object, ODBC, DSN and how to connect to a database. Please check the script code for more detailed information.
There are two ways to connect to a database: with a DSN connection or with a DSN-less connection.
(1) A DSN connection is more direct but it requires that the database be registered in the service provider's ODBC register. ODBC stands for "open database connectivity". Database products have drivers that enable external programs to access their data. ODBC drivers are used, for example, to import data from MS Access to Excel. In server-side scripts we use the same ODBC driver to import data from the database to our server-side script. But in order for this to happen, the database must be registered in the server's ODBC register with a name, called DSN (domain system name). The ODBC register needs to have information about the database product (e.g., MS Access, SQL Server, etc.), it's location in the server's hard disk, and the file name. The DSN does NOT have to use the same name as the original file name. For example, I have the following DSN names registered with our service provider: delivery (delivery.mdb); general (general.mdb); music (MusicInventory.mdb); orders (OrderEntry.mdb); HWnn (HWnn.mdb); Prjnn (Prjnn.mdb) -- nn is your number in the roster.
(2) A DSN-less connection does not require that you register the database in the ODBC register. All you need to do is specify the connection path diretly to the folder that has the database and supply the database name. This is a bit more cumbersome, but it has the convenience that you don't need to request your service provider to register the database. Just upload the database to your database folder and you are ready to go.