Unfortunately Jim, this is a mantra that was never repeated enough in the early days of Tango.
...... Explicitly scope all your variables, and avoid overusing User Scope except for the most critical information such as a person's Logon Session credentials or possibly a Shopping Cart array. ...... It's more work in the Studio, but it's a good habit to get into. Before v5, the "Default" scope was set to "User" in the t4server.ini file. This made many things about programming Tango very easy, but eventually this practice leads you into several traps with issues about Server performance and weeding through the army of temp Variables you collect when doing things like Looping and generating ResultSets. This is why Witango v5 has the "Default" Scope set to "Request" in the witango.ini file. "Local Scope" is not being phased, just renamed to "Request". "Request" is just a better name for "Local" because it's more descriptive about how to use this Scope, i.e., for Variables only available for the current execution of the TAF (a single HTTP Request). I know you're not excited about having to go back and edit all your variable assignments (and calls), but better now than later. If you use a good Text Editor (like www.textpad.com), you could experiment with doing a global search-and-replace on the file. TAF files are just XML text after all. Good luck. Cheers..... Scott Cadillac, Witango.org - http://witango.org 403-281-6090 - [EMAIL PROTECTED] -- Information for the Witango Developer Community --------------------- XML-Extranet - http://xml-extra.net 403-281-6090 - [EMAIL PROTECTED] -- Well-formed Development (for hire) --------------------- > -----Original Message----- > From: Jim Kass [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 18, 2003 2:39 PM > To: [EMAIL PROTECTED] > Subject: Witango-Talk: "Default" variable scope vs. Local > > > Hey Folks, > > I've noticed that on the 5.0 Dev Studio, all those variables > that were set > to use "Local" in an Assign action automatically get converted to > "Default" - I guess local is being phased out? > > The problem is that a 4.0 server doesn't see local and > default as the same, > and so the code breaks. Because the change is automagic, it happens > whenever I edit any file with these actions, and don't > explicitly set them > BACK to "local". > > Any known workarounds for this issue? > > Jim Kass > Web Developer > > -- > Forestweb: The Source for Industry Intelligence > Best Content -- Most Relevant -- Best Delivery > http://www.forestweb.com > (310) 553 - 0008 > > > ______________________________________________________________ > __________ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
