Clock

ASP script/code/whatever-you-wish-to-call-it runs on the server......

Now whatever it does, talk to a database, manipulate a local file, add 1+1, grab the server time, count to 1000 and do the hokey pokey......  whatever it does... the end result is HTML sent to the client (the computer/browser/human) on the other side of the connection who made the request....   once it delivers the HTML, the web server and client are through talking..... 

Now while you can have ASP "used in Javascript", be aware that the only time it'll do anything is when the page is rendered..

so...

in "test.asp" you have, and this is just a huge super slimmed down example:

<script language="javascript">
function ShowTime() {
 var CurrentTimeAsString = '<%= Now() %>';
}
</script>

if you "view" that page, you'd see something like:

<script language="javascript">
function ShowTime() {
 var CurrentTimeAsString = '6/25/2003 1:18:58 PM';
}
</script>

and at this point, ASP has done its job, page is rendered and delivered to the client, it no longer has a need to comminicate with the client, so the connection is severed

and this doesn't just go for ASP, it goes for PHP, and CF, and any other server-side language

Javascript on the other hand DOES run "real time" on the client.. so it has the ability to constantly update the page with something like, say, a clock....... so thats where the scripts on Dynamic Drive come in.... all that is pulling the time from the client and is in the realm of what it has access to (locally on the client's browser), it has abolutely zero access to the server at this post

Now this isn't saying that one couldn't write some code that "starts" from the "Now()" provided by the server, and then every second increments that initial time given by the server and constantly updates the page, but understand that the time will be off more and more as the javascript takes time to run