DB w/ Multiple Vis States and Attributes

[stusic]

Okay, I know that Autocad doesn't like duplicate attribute tags, but is there some workaround? I've got various versions of a block with multiple attributes for each. I'd add a block table to get the various different part numbers, model numbers, etc., but the blocks are physically different. I can't use uniquely named tags because I extract this out to an excel file, so there needs to be one column for "Part Number" (not a column for "Part No1", "Part No2", "Part No3", etc.). Has anyone found a way to do this? I've searched and can find some workarounds to slightly different problems, but none that address duplicate tags and physically different blocks.

Thanks for any help

[clshade]

Different Blocks can have the same Tag name can they not? I've just tried two simple ones and there seems to be no issue.
Is it the output to Excel that is the issue?
Or do the blocks fail to function as you wish?
Does changing the Value in one block affect the other block with the same Tag name?
If it was the case why would the same Block Inserted multiple times not also crash? (I know each gets a unique identifier but a name is a unique identifier as well.)

[stusic]

I'm having a problem when I use different blocks with the same attribute tags within the same DB, using vis states to change between them.

[clshade]

That would make sense.

Have you looked at anything regarding Nesting and working with Attributes?
There is a line to add to an extraction script to get to nested attribs.
I don't have experience with these though.

The current Help interface from Autodesk sucks so I'm not sure where that may get you.

[wroebuck]

Can you use the same attribute for multiple vis-states? You may not need to duplicate the attribute at all, just make it visible.

[stusic]

Well, then the problem is that each vis state is a different part, so the PARTNO attribute value would be different. Ideally, I'd like to add a block properties table that drives the vis state. Then I could have a flyout that users can change to the correct part, which would change the attributes and alter the vis state accordingly.

Maybe a lookup table? I don't have much experience with them, but maybe it could be done that way. I don't know how I'd go about it though...

[clshade]

Can you post the DynBlk or something that mimics it if it is proprietary?

[stusic]

Definitely. I'll upload it when I get home.

Thanks

[StDoodle]

You could use visibility states and an attribute with a field set to the Blockplaceholder -> [Name of Visibility State Parameter] to make things simple. Of course, if you have enough unique parts in each block, say by using various other parameters, it could get more complicated. It might be possible to hack something together with multiple fields, but that depends on your numbering system. Hmm.... would be curious to give it a go, though.

[stusic]

Okay, here's the example block. I tried to keep it simple, since I haven't worked it out yet. The first block has the block properties table for 2-pole. The second block has the BPT for the 3-pole, but has a vis state set up for 2-pole (with attributes for each). I'm really surprised there's not an easy way to do this, but if anyone can figure out a workaround, it'd be great - I've ripped all my hair out and would love to see how its done.