Marilyn -- I saw the same error when converting a 3.12 app to ND 4. I tried for a few hours to find a functional equivalent, but always got that same error message. I ended up clearing some key session objects, rendering the session useless, then outputting a redirect to the login page. I used an HTML redirect so that the login page would generate a new session ID; if I had load()'ed the login page from within the session, the session ID would have been preserved. If anyone knows of a more thorough way to kill a session in ND4, please share it! -- Ron Isaacson Diginexus Corporation [EMAIL PROTECTED] (215) 636-0850 x202 Marilyn Beaudreau wrote: >default Session Environment as a way to recover" This error is launched >when I use the following code: >CSpider.removedSessionID(CSpider.getSessionID()); > >This code worked fine in NDv3.1.2 but after migrating to ND4 I have >experienced problems... > >Has anyone seen this before? I realize that ND4 by default is >multi-threaded (and perhaps that could be causing a problem here) but from >the Control Center I am set up for one db transaction at a time. > >thx, >- M _________________________________________________________________________ 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]
