AutoLISP Help - Code not working on all machines

[asleafty927995]

Hello, I'm relatively new to the forum as well as LISP programming in general. I was hoping that I'd be able to get some help with de-bugging why the code I wrote will work on my machine and the rest of the team in my office (Seattle), but not with our satellite office in Dallas. The portion of code that I believe is not working is below:

 (command "-xref" "b" "*base"); this works fine and names the file consistently between locations
 (Command "regenall")
 (command ".explode" (ssget "_X" '((0 . "insert") (2 . "'*base"))) ""); this is what seems to break

A little background, we are a residential builder using AutoCAD 2014, and we have what we call a "Base" plan that is xref'd into the "elevation" file. The elevation file contains linework forward of a specific point on the house (this content is subject to change base on the elevation we decide to put on the house), and the Base plan contains everything from that specific point to the rear of the house (all the stuff that won't change). What I am trying to do is automate creating some background files for the engineering firm to utilize for different portions of the house. To do this I need to insert the xref and explode the block created by that insertion. The rest of the routine will then set the layers for the visibility I need and then wblock out the necessary files. I'm seriously confused why this will function without issue on my machine and that of my co-workers here in Seattle but will not function properly on our machines in Dallas. The entire code is attached for reference if necessary. Please let me know if there is something I'm missing. Thank you in advance for your time.

[Opie]

Is there a significance for the apostrophe within the block name of your selection set filter?

[peter]

The explode command for several releases would only allow for single items to be exploded.

I know 2010 is like that.

The work around for those releases would be to set the undocumented system variable qaflags to 1 explode the blocks and then set it back to 0.

You could also create a selection set and individually explode each block individually.

P=

[rkmcswain]

I can confirm that in 2014, you do need the 1 bitcode set in the sysvar QAFLAGS.

;; I suppose you could test the value the the bitcode 1 like this, but why?
;; Just save the current value, set it like you want, then set it back
;;  (if (not (eq 1 (logand 1 (getvar "qaflags"))))

;; begin
(setq qaflags (getvar "qaflags"))
(setvar "qaflags" 1)
(command ".explode" (ssget "_X" '((0 . "insert") (2 . "<blockname>"))) "")
(setvar "qaflags" qaflags)

[hmsilva]

The explode command for several releases would only allow for single items to be exploded.
I know 2010 is like that.
The work around for those releases would be to set the undocumented system variable qaflags to 1 explode the blocks and then set it back to 0.
You could also create a selection set and individually explode each block individually.
P=

Just to share,
from AC2010+, using the 'initcommandversion' function, we don't need to mess with 'qaflags' system variable
i.e.

(defun c:demo (/ ss)
  (cond ((setq ss (ssget "_X" '((0 . "INSERT") (2 . "<blockname>"))))
         (initcommandversion)
         (command "_.explode" ss "")
        )
  )
  (princ)
)

Henrique

[peter]

Good trick, I know for me... I hadn't seen that one.

Million ways to skin a cat in Acad.

P=

[cadtag]

if you're simply going to xref and immediately bind, why not just insert as a block?