I'm desperate... I have a site that has a hand coded section that runs a mini B2B auction system (written by someone else). To make the connection to the SQL server it uses a file called global.asa

It works great and I got it to interface with my part of the Dreaweaver ASP site fine. The problem is now I need to access a second database for some of my pages. As long as that global.asa file is there it will not make a connection, via DSN or a connections script. It just says unknown error. If I rename or remove that file, it makes the connection but the rest of the site does not work. I need to have the connection for my part of the site because there is a place on every page of mine that the users log into the auction.

any ideas ? PLEASE

Hi there,

You could add the general connection code inside another ASP file, lie Connection.asp. Then you can include this file in other pages that require it. In those pages, you can, for example, open the Connection, retrieve a recordset and close the connection again. This way, the general code (like the connection string) is all in once place.

If you do have to put your code in the global.asa file (depending on where in the global.asa you create your connection this may not be very recommended), I suggest you post the code for it, so maybe we can suggest place to put your new connection code.

Cheers,

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

Below is the code provided.

I have narrowed the error not allowing me to make other normal Dreamweaver connections to the code :
" if redirecturl <> "" then
                response.redirect redirecturl
            end if
            response.end
"
but I don't know how to fix it.

____________________________
<OBJECT RUNAT=Server SCOPE=Session ID=MyInfo PROGID="MSWC.MyInfo">
</OBJECT><SCRIPT LANGUAGE=VBScript RUNAT=Server>
    Sub Session_OnStart
        app_location="aspre"

        ' figure out who's coming in and where they belong
        session("url")=request.servervariables("URL")&"?"& request.servervariables("QUERY_STRING")
        if instr(session("url"),"distrib")>0 then
            login_status="distributor"
        elseif instr(session("url"),"purchaser")>0 then
            login_status="purchaser"
        elseif instr(session("url"),"cart_func")>0 then
            session("startshopping")=true
        elseif instr(session("url"),"admin")>0 then
            login_status="administrator"
        elseif instr(session("url"),"cron.asp")>0 then
            cron = true
        else
            login_status="index"
        end if
        if login_status="index" then
            redirecturl=cstr(Application("serverpath")&"defaul t.asp")
        elseif cron then
            redirecturl = ""
        elseif login_status="distributor" or login_status="purchaser" then
            redirecturl=cstr(Application("serverpath")&login_s tatus&"-login.asp")
        else
            redirecturl=session("url")
        end if

            Application("connectstring") = "DRIVER={SQL Server};SERVER=server;database=test;dsn=test;uid=t est;pwd=test"
            Application("server")="http://www.test.com"
            Application("serverpath") = "http://www.test.com/auction/"
            Application("fromaddr") = "[email protected]"
            Application("cronnotify") = "[email protected]"
            ' get admin email in functions.asp
            'Application("adminemail") = "[email protected]"
            Session("timeout") = 600
            if redirecturl <> "" then
                response.redirect redirecturl
            end if
            response.end
        end if
    End sub
    Sub Session_OnEnd
        response.write "Sorry, your session has expired!"
    End sub
</SCRIPT>

Hi there,

I noticed a few things in your post:

First of all, you may need to enable more detailed error messages in either your browser, or at the server (or both). For the browser (IE), open the Options panel, switch to the Advanced tab and disable Show friendly HTTP error messages. For IIS, open your site, click the Configuration button on either the Directory or Home Directory tab, and then switch to the Debugging tab. Make sure that Send detailed ASP error messages to client is checked.

Once you do that, you'll probably get an error like this: Once you look at like 42, you'll see that you have one End If too much. Once you remove it, the global.asa is OK, and your pages will run fine. At this point, you could add additional connection strings in the Application scope.

The last thing I noticed is the Session_OnEnd. This event will fire when the session times out or is destroyed. This means that the user is no longer connected. So, even if you have a Response.Write statement there, your client will never see the "Sorry, your session has expired!" appear.

Hope this helps,

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

Thank you Imar,

That was a huge help! I have things working great now.