load vlx file

[aaryan]

Hi all,

 

I have a vlx file which is provided by my colleague. He used to work it with autocad 2005 version. but when i try load the same file in latest version an error is coming.

; error: bad argument type: stringp nil

Is there anyway to fix this error.

 

Regards

Aryan

[pBe]

Yes there is...

A lot of guesswork

 

Seriiously. its a lot easier to track down the problem if we know what to code is all about.

[aaryan]

thanks pBe

But i think we cannot edit the vlx file...

It was made to be worked with Acad 2005 may be that is one of the reason

[pBe]

of course we cant edit. and SHOULD NOT..

Knowing what the code does will narrow the problem a lot.

Lets say the code workded before for a certain type of entities like Text Entities..

it mght be processing a TEXT entities and not MTEXT..

 

Give us a description of what it does. THEN we'll see what we can do..

[aaryan]

Its a copyright program written for making survey charts and profile and much more. Along with this vlx file there are some arx file for 2005, dll and cui file 2005.. I cant upload it here as it is copyright..

Can you just suggest me something..

BTW I am thnakful for your replies...

[pBe]

From the looks of it, based on the error message. problem with string value

 

(setq str "Banana Cake")

(strcase str)

"BANANA CAKE"

 

(setq str nil)

(strcase str)

; error: bad argument type: stringp nil

 

It appears the routine is evaluating a string value and passing it ti a variable name

Now if for example you retrieve string value of a TEXT entity

 

(cdr (assoc 1 (entget ent)))

"123"

(> (atoi str) 10)

T

if by somehow the entity is MTEXT with formating

"\\A1;\\pxql;123"

(if (> (atoi str) 10)

nil

then you pass the value for evaluation. you will get

 

; error: bad argument type: stringp nil

 

Bottom line, there are entity types in newer cad version that old programs do not recognize. especially when it involves Native commands.

Check the entity types you are using then and comapre it to the drawing where the lisp program crashes

Edited January 23, 2012 by pBe

[BIGAL]

You need to go back the the original suppliers and seek an updated version it will probably cost you. The big message here copyrighted.

[pBe]

My take on this issue is to write a new code, thats why i asked for a description and not the code itself.

But then again... an updated version of the program from the orignal author would be a better option and YES it will probably cost you.

[aaryan]

Thank You so much