Protect a Block how?

Dear friends,

How can we protect our Blocks with Attributes from the command "Block Edit" and other edit commands like "REFEDIT"..

Yours,

Muthu.

Paranoia runs deep.

Protect them from whom? What do you fear the other person(s) will do to/with your blocks?

I thinks he means protecting the block so that others cannot "refedit" them. So the block allways remains its original format.

Don't know a solution however...

At least not without a lisp running in the dwg.

To prevent less experienced users to access some commands may UNDEFINE those commands on their workstations.

Regards,

Less experienced users are somehow going to figure out how to undefine commands. Really? You are seriously worried about that happening? And how do you think they are going to stumble upon that?

"AutoCAD allows users to “undefine” its commands. This is used primarily by programmers when they want to create a custom version of a particular command."

Did you hire some former programmers at CAD techs?

Locking a block is virtually impossible. However, Lee Mac did come up with a couple of Lisp routines that might be of interest to you. They are contained within this five page thread. Start at the beginning or you may miss something.

http://www.cadtutor.mobi/forum/showthread.php?t=47366

Less experienced users are somehow going to figure out how to undefine commands. Really? You are seriously worried about that happening? And how do you think they are going to stumble upon that?

 

Did you hire some former programmers at CAD techs?

My suggestion was to undefine the REFEDIT command for the user(s) that aren’t allowed to edit those blocks. Maybe I wasn’t clear enough. Sorry for inconvenience.

Regards,

Whatever happened to trust?

No problem and no apology required. Thanks for the explanation. Good luck.

Paranoia runs deep.

 

Protect them from whom? What do you fear the other person(s) will do to/with your blocks?

My engineers will do anything to cut corners, all under the guise of 'efficiency'. What they don't realize, even though they've been told, is that it takes longer to clean up their mess than to do it right the first time. It's not as simple as just asking them to do it right. So I feel for muthu's desire to lock the blocks.

BLOCKEDITLOCK variable set to 1 specifies that the Block Editor cannot be opened. Obviously it can be changed back to 0, but if they don't know, they can't change it.

As for refedit, I am fortunate in that my engineers only have LT, so it's not really an issue. I do, however, check the box upon block creation that does not allow exploding.

Whatever happened to trust?

 

No problem and no apology required. Thanks for the explanation. Good luck.

Education good.

If you can't trust someone, whey are they there?

If an engineer can figure out how to define a command then they can find blockeditlock and change it. It is not foolproof.

And you can get around not being able to explode a block too.

Anyone smart enough to effectively use the Internet can find the solutions to the obstacles you put before them. Human nature being what it is.

Yes, I understand what the OP is trying to do but in the end if the user wants to circumvent these obstacles he/she will find a way to do it.

Not that I can create this but what about this:

If you would have a lisp running (through acaddoc.lsp) that has a reactor wich is triggered by the command blockeditlock you could "refuse" acces to this command.

As said, I can't make it...

Anything is possible.