Wait a minute, I think I'm back to ESC being evaluated at the same
time as a function. Still working on this....
You would possibly store the ESC() as a string in your variable
tables, then evaluate it with EVAL(pointer to ESC())
What I'ma having difficulty figuring out is the following output in
the Messagebox:
I'm still
"Working on it"
;
Exec QuoteEscape OFF
MESSAGEBOX("ok","I'm still"++ESC(\n\")++"Working on it"++ESC(\"))
; assuming your system has this ON
Exec QuoteEscape ON
QUIT
I'm confused how you could do this without major recoding... but am
confident that this is the key to the escape char issues.
maybe:
MESSAGEBOX("ok",ESC(I'm still\n"Working on it"))
Ted
> Agree, ESC() would occur when ?c..c is done. (I was stuck in an
> older
> > Ignoring &(), the processing of an expression means that tokens
> > like strings always have to be parsed before calling functions.
> > PowerPro's parsing is not designed to allow functions calls to
> > determine how to parse the following characters.
> >
> > Thats what setstring is a completely separate statement.
> >
> > But anyway, I don't understand how ESC would accomplish anthig
> > different from ESC, even if it were possible to implement.
------------------------ Yahoo! Groups Sponsor --------------------~-->
Yahoo! Domains - Claim yours for only $14.70
http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/JV_rlB/TM
--------------------------------------------------------------------~->
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/
