I have a JavaScript that uses setInterval to call a function every 5 seconds. This function reads a record from the database, use DOM to replace the data in my table. I added a column that shows a running timer just to make sure that the data was replaced correctly using DOM. After I launched the page, I made an update to the column in the database. The page kept displaying the same value from the first time the page was loaded. The column for the timer continued to change correctly. So, I believe that the recordset returned wasn't refreshed during all subsequent called to this function using the setInterval method. If I refreshed the page, I got the new value from the database. Does anyone has this experience and know how to fix it? See my sample code below:

In the Head section:
var call_work_timerID = 0;
function StartCallWorkTimer()
{
<%
    var adoConnection = Server.CreateObject("ADODB.Connection");
    adoConnection.Open("DSN=ic613; UID=oadba; PWD=oadba");
    var adoRecordset = Server.CreateObject("ADODB.Recordset");

    var QStr= "my query string that finds one matching record";
    adoRecordset.Open(QStr, adoConnection);
    if (adoRecordset.Eof == false && adoRecordset.Bof == false)
    { X= adoRecordset("idleavaildur").Value;
      Y= <my current time in milliseconds>;
    }
    <Use DOM to replace my X and Y fields in my table here>
    adoRecordset.Close();
    adoRecordset = null;
    adoConnection.Close();
    adoConnection = null;
}

In the Body:
<input type=button name=btnStop1 value="Start" onclick="javascript:call_work_timerID=setInterval( 'StartCallWorkTimer()',5000);">
<input type=button name=btnStop2 value="Stop" onclick="javascript:clearInterval(call_work_timerI D);">

in JavaScript: or simply
in HTML

Always:),
Hovik Melkomian.

I see the <% and that tells you are writing ASP with javascript, correct?

Take a look at the source HTML for the page. I think you will not see the code that handles the database, but only the code that sets the dynamic values using the DOM. I imagine you are switching back from ASP (%>) and writing the DOM calls to update the page's text with the new values from the database with some mixure of javascript calls with ASP values (in <% %>) intertwined then switching back into the ASP code (<%). While this works, it's not doing what you want because the server-side hit to the database is only being made once and you are providing a static chunk of update code that is being called repeatedly by the browser using the interval timer. In order to do what you want using ASP you are going to have to refresh the whole page at the server.

Peter
-------------------------
Work smarter, not harder

Didn't we cover this in two previous threads:

http://p2p.wrox.com/topic.asp?TOPIC_ID=11767
http://p2p.wrox.com/topic.asp?TOPIC_ID=11765

The same principle still applies: client side code runs at the client, server side code at the server. When the page first loads, the server side block runs, and the output is inserted between the { and the } of the StartCallWorkTimer mehtod. Then the page is sent to the browser where the method will run, using the same output from the server side code.

It looks like you're missing a few important client-server concepts....

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to: Bearsuit by Tindersticks (Track 11 from the album: Curtains)

Hey, thanks a lot! I did forget that the server side code only gets executed once.