I have a "*Script SetString avar avalue" declared in a command list item and it triggers a "Variable used before being declared" error from code in the "more commands" listbox when the command list item is first used. It is a nusanace.
Yes, I have the option to warn-about-using-variables-before-declaration enabled and would prefer to keep it enabled. I put a "global avar" declaration in a schedule item that happens at "startup" but that doesn't resolve the issue. I tried "*Script Global avar" and then added an assignment line to the "more commands" listbox, above the code that is actually triggerng the error. The consequence is that nothing is executed in complete silence?? (which is another question but let's stay focused :)>) I tried using an Assign. Same as using a SetString. Aside from moving the entire shebang into a script file and/or disabling the b4defintion warning, how can I resolve the error. re, evan Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
