Good Lord! Thanks for the warning. I have an app that talks to a CGI via POST and it sets the parameter list in form-encoded fashion (var1=value1&var2=value2). It never gave me trouble but to play safe I guess I'll have to change all occurrences of the literal "&" to CHR(38).

>... that macro expansion works inside of quotes? I just ran across this in someone else's code, and thought that it was a bug for sure. You learn something new every day, although I'm not sure when I would have the need for this. More importantly, this behavior could produce a bug if you're not expecting it . An example is below.
>
>

>cMacro = "Test"
>? "&cMacro"  && returns "Test"
>? cMacro  && this is how most people would do it
>? "&cAnotherMacro"  && returns "&cAnotherMacro" since variable doesn't exist.
>
>Example producing unwanted results:
>D = "Test"
>? "R&D"  && returns "RTest"
>

bye