Are you aware that WiTango 2000 will serve up 3.x taf files without modification? Yes there were a few gotchas but they were very very few and far between.
You might want to test your existing stuff, unmodified, being run through WiTango 2000. That will allow you to run a much smoother conversion of the actual TAF files when you need to convert them (i.e. to take advantage of a new tag). Hope this helps, Steve Smith Skadt Information Solutions Office: (519) 624-4388 GTA: (416) 606-3885 Fax: (519) 624-3353 Cell: (416) 606-3885 Email: [EMAIL PROTECTED] Web: http://www.skadt.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Web Dude Sent: June 7, 2002 5:16 PM To: Multiple recipients of list witango-talk Subject: Witango-Talk: Stupid Upgrade Questions Okay NT 4.0 SQL 7 IIS 4 I have been dreading this and putting it off for a long time, but it is now time to upgrade my server running 3.6 to WiTango 2000. I have some questions about the upgrade process. Are there any caveats or suggestions for going through this? One of the problems I have is that 6 of my major sites run through an SSL domain and I know I can't pass variables from 3.6 to 2000 or back again, so I need to do this all at once and get it up and running. I will be doing an all nighter for this and I need to get all my ducks in a row (quak quak). I need to work on syntax and have a general question on whether this will bomb 2000... Is it okay for the following? <input type ="text" value="<@column "product.id">"> or do I need... <input type ="text" value="<@column 'product.id'>"> Will this work when I upgrade? I know that nested quotes (and have fixed all of them) when assigning and calling variables are important.. ie <@ASSIGN test "<@column 'product.id'>"> But what about nesting in forms? Any suggestions and other related problems that may arise are welcome! Thanks!! -- ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
