Table issues...

[rgorman]

Or- how can I lock them down so they CAN'T be exploded? We have several standard tables that are used for legends, reference drawings, etc... They are brought in as blocks (exploded) through the tool palette and work perfect. But thanks to a few in-DUH-viduals who can't keep their heads out of their butts and learn something new, I constantly come across these tables after they've been exploded into lines and text. OTHER than undefining the explode command for everyone (it does come in handy once in a while) can these tables be locked so they CAN'T be broken. Putting them on a locked layer won't work because, surprisingly, they will read the note that says it's on a locked layer and unlock it.

Thanks-

R.

[Anonymous]

I'd like to know as well. The only way would be to make them so they can
not be exploded, locking is not an option because you will alway have the
ability to unlock to edit.

You can lead a hors er.. donkey to water....

ACote
wrote in message news:5968828@discussion.autodesk.com...
Or- how can I lock them down so they CAN'T be exploded? We have several
standard tables that are used for legends, reference drawings, etc... They
are brought in as blocks (exploded) through the tool palette and work
perfect. But thanks to a few in-DUH-viduals who can't keep their heads out
of their butts and learn something new, I constantly come across these
tables after they've been exploded into lines and text. OTHER than
undefining the explode command for everyone (it does come in handy once in a
while) can these tables be locked so they CAN'T be broken. Putting them on a
locked layer won't work because, surprisingly, they will read the note that
says it's on a locked layer and unlock it.

Thanks-

R.

[Anonymous]

Sounds like you are skimping on training, guidance, more training, peer
support, group reviews, training, and oh yeah, a big stick (HR and Upper
Management).

--
Dean Saadallah
http://LTisACAD.blogspot.com
Add-on products for LT
http://www.pendean.com/lt
--

[ASCunningham]

I had the same problems so I added this to our mnl file. Thanks to Doug who wrote the lisp.

I haven't had a problem since with a table being exploded. Of course you can explode them if you use .explode or .x etc

;;;=== Added to redefine explode to not allow exploding of acad tables =============================
;;Undefine the explode command
(command "undefine" "explode")
;;New command definition that excludes tables. You could refine
;;this to select only explodable objects.
;;D. C. Broad 2008
(defun c:explode (/ oce ss)
(princ "\nSelect objects to explode")
(if
(setq ss (ssget (list (cons 0 "~ACAD_TABLE"))))
(progn
(sssetfirst ss ss)
(setq oce (getvar "cmdecho"))
(setvar "cmdecho" 0)
(command "_.explode")
(setvar "cmdecho" oce)
)
)
(princ)
)

[rgorman]

If that works, your beer is on me at the Beer bust... Sure looks like it might... I'll give it a whirl on my box, then casually plop it into their acaddoc.lsp files while doing other maintenance

thanks...

Oh, wait.. mnl file? would it work from the acaddoc file? Maybe a tweak is needed for that? Message was edited by: RAGorman

[coviepresb1647]

"But thanks to a few in-DUH-viduals who can't keep their heads out of their butts and learn something new"

Have you or other competent person in your organization taught it (i.e, "(bringing) in as blocks (exploded) through the tool palette and work perfect") and how tables function to those individuals?

Message was edited by: coviepresb1647

[Anonymous]

Have you dealt with someone who doesn't get it (or want to) no matter how
many times you tell them? That's the kind of people Ray is referring to.

--
Joshua Tapp

wrote in message news:5970045@discussion.autodesk.com...
"But thanks to a few in-DUH-viduals who can't keep their heads out of their
butts and learn something new"

Have you or other competent person in your organization taught it (i.e,
"(bringing) in as blocks (exploded) through the tool palette and work
perfect") and how tables function to those individuals?

Message was edited by: coviepresb1647

[coviepresb1647]

Yes, I have. It was not clear the nature of those individuals (whether hard and stubborn or hard and desirous). Those that desire to learn and are hard of learning to get it eventually whilst others who don't desire to learn obviously don't get it. Hence, my question.

[rgorman]

they don't get it, they don't want to get it, and they act as if I'M doing something to undermine their abilities (which they don't have in the first place).

But anyhows- it DOES work when plopped into the acaddoc.lsp files. It prevents exploding a table but leaves the command available for other entities. At least the ones that I have allowed the ability to explode. Generally, ALL of our blocks brought in through the TP are set so that they cannot be exploded. And thankfully they can't figure out how to change it.

[ASCunningham]

I would think that it will work in the acaddoc file. That gets loaded at each session of ACAD right?

I can tell you that I put this in about 6 months ago and haven't had a problem ever since. Seems too easy, but it does get the job done. BTW if you have an experienced Acad user they might figure out how to explode the table, but I have not run into anyone here at my workplace that has figured that out.

[coviepresb1647]

LOL (at their response). i see your very good point and the good solution. and of course, if they ask how, refuse to tell their stubborn minds. Message was edited by: coviepresb1647

[rgorman]

It's funny, if I told them how to do that- they WOULD remember because they would rather work with the text and lines than learn how to use a table. So I walk a fine line....