Nick,
I've had this happen too. My (dumb) workaround is to add a RESUME command
immediately after the point in the script where it stops running.
Something like this:
...
SomeCommand
(SomeLisp)
resume
Regards,
Steve Doman
"Nick Fuller" wrote in message
news:CBF2818589CC576A359F3800B23CDA14@in.WebX.maYIadrTaRb...
> I am a an "Old School" user that still likes to use scripts for various
> redundant actions. I am running a script that goes through various
standards
> AutoCAD commands and performs them on an array of files. Within the script
a
> lisp routine in initiated. At the completion of the routine the script
> (without errors) simply stops. Is this a result of running lisp out of a
> script? If so, is there a way to get around this, other than pasting the
> lisp into the script? Any help would be greatly appreciated.
>
>