Changing an attribute field in several thousand blocks...ARRGH!

[Anonymous]

I have a few thousand blocks that I have to make the exact same change to and then put onto tool palettes.  These blocks have an attribute in them that is supposed to match the name of the block for data extraction purposes later on.  The person who initially made the blocks didn't bother to enter the indivdual attribute field correctly the first time around (just entered "X")...hence the large, repetitive, boring task ahead of me.

It took me several days to figure out a procedure to make this work.  I've attached the procedure I'm following; I think there are too many steps in here.  Could someone please look this over and tell me how I can make this task shorter/easier?  Thanks in advance!

[Anonymous]

This may turn into a rant very shortly.  I'm just now trying to cut down on the steps by exploding the block, changing the Attribute text, then remaking the block.  BUT....I still have to give it a different name, or it wont come off the palette correctly!  Attention AutoDesk:  What is the friggin' point of having any options for editing on the palette menu if the darn block won't reflect the changes???  AND, I've redefined the block before I even put it on the tool palette, so just WHERE WHERE WHERE WHERE is the palette getting the OLD attribute value from if the block has physically been redefined?  Isn't that the whole point of redefining a block, to WIPE OUT THE OLD DATA??  There's some black hole of data in the drawing that won't go away!!!!

[Anonymous]

My overall process resolved itself, albeit not in the manner I described.  This entire process involves taking pre-made blocks that have two attributes in them, and correcting one to show a specific value immediately upon insertion.  As I previously described, the blocks keep screwing up the attribute when I copy them on to and then pull them off a tool palette.  However...

What I perceived as the second phase of this large project involves grouping 6-10 of these blocks into their own nested block with a visibility attribute, then placing THAT nested block on Tool Palettes.  In this process, when it comes time to use the block in a drawing, the nested block gets dragged of the palette, the desired visibility state is selected, and then the nested block is exploded, leaving behind the desired single-level block.

Going this route, the initial single-level block did not require ANY modifications.  This was a relief beyond measure, as now I can just proceed with making all the nested blocks and avoid the 20-step process of fixing that darn attribte that I mentioned earlier.