t4server.ini DefaultScope=user
I might just luck out here. Thanks! Tom _____ From: Robert Shubert [mailto:rshub...@tronics.com] Sent: Wednesday, November 23, 2011 9:47 AM To: Witango-Talk@witango.com Subject: RE: Witango-Talk: Scoping Variables Tom, Please doublecheck in your tango.ini (or witango.ini) that the DEFAULTSCOPE option is set to local. It may be set to user, since the change to the local/request scope by default was not made until v5.0. If it is set to user, then my earlier post applies to your situation. Robert From: Tom Ferguson [mailto:t...@idealtogo.com] Sent: Tuesday, November 22, 2011 9:22 PM To: Witango-Talk@witango.com Subject: RE: Witango-Talk: Scoping Variables Thanks Ben _____ From: Ben Johansen [mailto:b...@webspinr.com] Sent: Tuesday, November 22, 2011 7:37 PM To: Witango-Talk@witango.com Subject: Re: Witango-Talk: Scoping Variables to answer Tom's question. when you specify no scope it is set to LOCAL scope in 4.5 and in TetraScripe the default scope is REQUEST, you should be fine because you didn't specify scope, you are also ok if you had specified LOCAL literally because, LOCAL = REQUEST scope. On Nov 21, 2011, at 11:57 AM, Tom Ferguson wrote: Not to hijack WebDude's thread, but I'll be doing the very same thing soon, going from 4.5 to TeraScribe. I have no scopes specified either. What happens if I leave the scopes as is? Thanks! _____ From: WebDude [mailto:webd...@cipromo.com] Sent: Monday, November 21, 2011 1:18 PM To: Witango-Talk@witango.com Subject: Witango-Talk: Scoping Variables Hi Folks, I am currently preparing to upgrade from version 4, probably to version 6 and then up to Terascribe. I remember that syntax and scoping of variables have changed. I am trying to prepare as much of the old files as possible before upgrading. I will probabaly have more questions to come, but I am going to take this a step at a time. First question is concerning scoping variables. Presently, almost all variables are not scoped so I am going through the ardious process of straightening these out. A few questions, if you don't mind... I would assume that you need to scope all <@ASSIGNs Most of the applications have no scope assigned to them presently. Of course, the default for this is "user" in the version I am using, but I am going to go through each assign and scope it appropriately. Almost all are goinmg to be scoped as user, but I have a few that can be scoped as local. Whenever calling on the variable, such as <@VAR blah> I am also going to assume these need to be scoped as well, as is <@VAR blah scope "user"> Do I need to scope any <@PURGE variables? When calling a local variable, should these be scoped as well? i.e. <@VAR blah scope "local"> What exactly is the request scope? This will be for futue reference. It appears to be the same as the local scope. When I upgrade, will I need to change all local scopes to request scope? Is this just a neam change to avoid confusion Thanks for any help! _____ To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body. _____ To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body. Ben Johansen http://www.webspinr.com b...@webspinr.com Phone: 503-477-5409 Mobile: 360-600-7775 _____ To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body. _____ To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body. _____ To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body.
