When codelock acts this way, sometimes the only way to fix it is to trick it
SET VAR vCommand = 'LOAD tableview FROM filespec;NOCHECK;NONUM'
&vCommand
This will be run correctly because codelock does not have a clue what is in
the command string and cannot modify it. It will get executed correctly at
run time.
One gotcha I have found with codelock. It will think the quote is ' even
when it is "
I always put
SET QUOTES=''''
or
SET QUOTES=""""
at the top of every APP file. That way I know codelock will get it right.
It does not even have to be in the code your are executing, just a stub
program at the top of the file:
$COMMAND
BOGUS
SET QUOTES=''''
RETURN
-- OTHER MODULES FOLLOW
In case some of you have not seen my SET QUOTES syntax before, let me just
say that this syntax ALWAYS works without setting QUOTES=NULL first. It
works this way because of the way the R:BASE interpreter works. It has
worked this way as long as I can rememember. Just tested it in System V and
it works exactly the same.
R:BASE will always interpret it as SET QUOTES=' regardless of what the
current quotes setting is.
Likewise, SET QUOTES="""" will always be interpreted as SET QUOTES="
--Dennis McGrath
