Shouldn't be an issue I just tried <@ROWS> <@ASSIGN test VALUE="<@COLUMN "PopUps.PopNbr">" SCOPE="local"> @@local$test </@ROWS> worked fine
the only side effect is that it doesn't colorize the rest of the line in the editor correctly when I moved code it was open up and save, but there is no going back if you save over the top of the 3.6 named file. So make a backup ;-) If you need help during this time, let me know off list Ben Johansen - http://www.pcforge.com Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm Latest downloads & List Archives @ http://www.witango.ws -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Web Dude Sent: Friday, June 07, 2002 2: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
