This is a general situation with any web application.
The main different between a web application and a client/server 2 tier
application is that there is no permenent connection.
In the two tier application the client have a copy of everything and all
variables are there for the lenth of the whole session.
For web application it is there for the length of just the processing of one
page (or one submit by the browser to the web server).
In ND that is one web event, which is typically a click of one button or
href.
Before you use any variables in the page you need to initialize them.
Typically you save the variables in seesion objects/ or sometimes in page
session objects/ or once in a while a globol session objects.
You could initialize them in your web event if it is unique to that web
event.
Or you can initial them in some common events like this_onbeforedisplay,
onbeforeload, onafteralldataobjectexecute etc.
Try test you project using at least two cp workers and two clients per
worker.
Normally if you forget about initialization you will see some funny
unexpected result if you use multiple workers.
If you use one worker and is only testing it using one brower you will not
see those problems because you will always use the same worker and the "same
copy of the page". S
So what you left behind the last time you cuse the page is still there.
You can get all those condition out by running two copies of you browser and
use them back and forth.
(run the 2nd copy from the short cut and copy the 1st window)
This would simulate two different user.
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
