Variables in request scope persist only for the duration of one web server "request". In other words, you click on a link or submit a form that runs some Witango file. That file may branch to other files as part of that request, but ultimately the request is complete, and the result is returned to the web server. At this point, the request scope variables are purged.
Stefan
At 11:08 AM 12/22/2003, you wrote:
The way I read the description of request scope it should remain for the execution of the whole application. I assume then that course.taf is an application and as long as I am executing things in that application I will see the same request scope variables.
But it seem to not work as expected. If I execute another search action even though I don't reassign the variables all my request scope variables are gone.
I seem to remember it working this way with local scope in TK2 but I thought it was fixed in V4.5 even.
I can work around it if any search action will wipe my request variables but I would like to know for sure how it is supposed to work.
Dan
-- Dan Stein Digital Software Solutions 799 Evergreen Circle Telford PA 18969 Land: 215-799-0192 Mobile: 610-256-2843 Fax 413-410-9682 FMP, WiTango, EDI,SQL 2000 [EMAIL PROTECTED] www.dss-db.com
"When you are born, you cry and those who love you rejoice. And if you live your life as you should, when you die, you rejoice and those who love you cry."
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
========================================================
Database WebWorks: Dynamic web sites through database integration
http://www.DatabaseWebWorks.com
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
