Help | Site Map
Connecting Tech Pros Worldwide
 
 
LinkBack Thread Tools
  #1  
Old July 19th, 2005, 02:20 PM
Elie Grouchko
Guest
 
Posts: n/a
Default Server.Execute() & Application.Lock

Hi

In Page1.asp I am calling Server.Execute("Page2.asp"). Before calling
Server.Execute(), I set an application variable to a value that it is
important for me to know that it doesn't get accessed by another ASP page
before I call Application.unlock in Page2.asp, that is why I use
Application.lock.

According to the documentation, Application.lock gets automatically unlocked
when the ASP page terminate, I want to confirm that calling Server.Execute()
doesn't automatically unlock the application, i.e that Page2.asp will start
executing when the application is still locked.

Many thanks

Elie Grouchko


 

Bookmarks

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

What is Bytes?

We are a network of experts and professionals in IT and software development that help one another with answers to tough questions and share insights. Get the best answers to your questions from over network members.
Post your question now . . .
It's fast and it's free

Popular Articles