Kicks
Sanity doesn't hate anything.. it warns you when it finds a syntax error such as mismatched paren or quote, or an unterminated clause. Then, it will prod you when your code doesn't follow some well recognized best practices, such as placing vars or macros inside strings.
Sometimes it's not possible to eliminate every Sanity warning without code changes. For example, Sanity doesn't handle quoted strings spread across multiple lines. This is by design, as we want you to be warned of the condition - we'd have no way to know for sure. It's entirely legitimate to put "$" in a string. Sanity will warn simply because it COULD cause a problem, not because it WILL. You need to interpret the output of Sanity and decide if the warning applies to your code. KixForms and Execute statements will particularly throw these warnings for valid code.
The warning was valid - you had strings inside quotes. You can choose to ignore the warning because the code works as intended, or modify it as Allen has shown to eliminate the warnings, but verify that the code still works. It really depends on whether you want your string to have variable data or variable names in it, depending on the setting of NoVarsInStrings.
Glenn
_________________________
Actually I
am a Rocket Scientist!
