The unique names did it, although I'm not really sure why.  I have two modules that are different AFTER 8 letters, and they both run just fine.  Besides why would the trace work, but not running normally?

Bit, thanks for the idea, anyway.  It made the difference.

Lawrence Lustig wrote:
If I dump that block of code into a cmd file, it works perfectly.
    

I noticed that you are running from a codelocked multi-block APX file. Make
sure you check for program or menu blocks that are not unique in the first
eight characters.  You cannot, for instance, have a program and menu block with
the same name.

Try copying your source file, and removing all code in the called program
block, then putting a single PAUSE or WRITE statement in there and
re-codelocking.  Does it execute?  If not, the problem is calling the block. 
If it does execute, then the problem is within your code block.

Next, put the text of the code block into a separate file, without other
blocks, and try RStyling it.  Any better results?  If nothing is revealed, try
codelocking this file as a stand-alone binary file.  Does it run?  If not,
there is something in your codeblock that is causing an alergic reaction to
CODELOCK.  Check for odd line continuations, tab characters, strings continuing
across line breaks, ampersand and dotted variable mix-ups, particularly
"clever" macro substitutions, and so on.

--
Larry


  

Reply via email to