Terminate A Asynchronous Script
i ran a code with xmlhttp object that sende an email in asychronous method somehow its keeping sending me mail , about 2500 so far. does any body knows how do i terminate this code?
View Repliesi ran a code with xmlhttp object that sende an email in asychronous method somehow its keeping sending me mail , about 2500 so far. does any body knows how do i terminate this code?
View RepliesWe have an asp.net application that will also use MSMQ. When a client makes
a request, we want to check several databases and put each response in MSMQ.
We don't want the client to wait for all responses to come back. We were
wondering if there is some component that will sit on the client and listen
for call backs from the the server. We are also concidering using AJAX to
poll MSMQ every 5 seconds and show any new responses. Has anyone had any
experience with this?
Is there a way for an administrator to terminate ASP sessions if I know the ASP Session IDs that I want to terminate? Session.Abandon only works on the caller's session. Is there something like Session.Kill(SessionID) ?
View Replies View RelatedI understand that I can use "Exit Sub" to terminate an subroutine. However,this does not prevent everything before the "Exit Sub" from processing and displaying. Now, if I can't determine if a certain condition is met or not met until later in the subroutine, how can I prevent any parts of the code from displaying?
For example:
Code:
Sub XYZ
Response.Write "Table Header"
For 0 to all user's online
If user's page is an product page, then
Response.Write Page_Name
Y = Y + 1
end if
next
If Y <> "" then
Exit Sub
End if
End Sub
I'm using an access database and found following problem :
I have a table X with 2 records : record 1 & record 2. I execute following
procedure with 2 steps :
1. The procedure deletes records 1 : connection.execute "delete from X
record 1"
2. The procedure adds record 1 again using the recordset object.
Result : nothing happens !
I have the feeling that the "delete" statement is executed AFTER the "add
record" statement. Or the "delete" statement did not finish before the
start of the "add record" statement (= asyncrhonous processing).
Can somebody explain me this behavior ? I have this problem only when using a MS Access database and not with an MS SQL database.