DSN & global.asa

Here is a quick test to see if your global.asa file is "firing" and configured for your Data Source Name (DSN).

1. Create a new page with FP2K in your SF2K web's root and name it something like dsntest.asp. It does have to be an asp file.
2. Edit the new page in HTML view and add the following line to the very top of the file: <% Response.Write "DSN_Name = " & Session("DSN_Name") %>
3. Save the file and view it in your browser.
4. If you do not see anything after the equals sign, your global.asa is either not firing or is not the standard SF2K global.asa or has not been configured for your DSN.
5. If you see something like: DSN_Name = DSN=mydsn;DRIVER=(Microsoft Access Driver (*.mdb)), and the DSN_Name is the one you intended, your global.asa and DSN are functioning.

If this test fails, you should check or do the following:

1. Make sure you or your web host have configured a System DSN on the server that points to your SF2K database file.
2. Make sure the global.asa file in your web's root is the one shipped with SF2K. If in doubt, import a fresh copy from the SF2K template files.
3. Delete any existing database connection using FrontPage 2000 and create a new one, which uses your System DSN. Make sure you verify the connection.