For us it wasnt all that tedious moving from tango2000 to witango 5. the biggest problem was that like Wayne said, unscoped variables would be in the request (local) scope instead of the user scope by default.
You can change this behaviour in your witango.ini to make the default scope user and that clears up your problems there. It is good practice though to scope your variables. Different scopes act differently so it makes sense to be very specific about how you want your variable to act by defining the scope. You may hear things about the "request" scope, but request and local are one and the same so thats nothing to worry about (: we had a very nice and simple move over and things are running better than ever ever since. ----- Original Message ----- From: "Wayne Irvine" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 12, 2004 10:24 PM Subject: Witango-Talk: Re: Witango-Talk: > > > I want to upgrade from Tango2000 to Witango. Can I port the code > > that is currently running in Tango2000 without any alternation to Witango. > > > The major difference between T2000 and WT5 code is that the default VAR > SCOPE is USER in T2000 and REQUEST (or LOCAL) in WT5. > > Any code you have written that doesn't stipulate SCOPE will be effected. > > There may be other differences with regards to datasources and paths, but as > you haven't specified I can't comment. > > Basically you can do it but it will probably be a tedious job. One I am > currently about to embark upon. > > Wayne Irvine > > Byte Services Pty Ltd > http://www.byteserve.com.au/ > [EMAIL PROTECTED] > Ph 02 9960 6099 Mob 0409 960 609 Fax 02 9960 6088 > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
