Since Visual LISP "compiles" the text into byte codes, the scroll-back
of text isn't really available any more. However, you can have your
customer load the following:
(defun *error* (msg)
(vl-bt)
(princ)
)
and then run your program. The error will cause a ton of information
to be printed out, which you can use to figure out where the error
occurred.
jrf
Member of the Autodesk Discussion Forum Moderator Program
Please do not email questions unless you wish to hire my services
In article , Jeffds wrote:
> Hi,
> I have just started using 2000.
> In R14 and back when a
> run-time error occured in Autolisp the code would scroll onto the
> screen at the line it crashed at. In 2000i this doesn't happen. Is
> there a way to toggle this on to see where the routine is crashing.
> I have a client in Perth (I'm in Melbourne) who is having a probelm
> with a routine I have written for him. It works on my installation
> but not his. He is getting an error: stringp nil. So some variable
> has not been correctly initialised but I can't tell where!
> Thanks
> for any help.
>