Message 1 of 1
strange Group behaviour
Not applicable
07-20-2009
10:19 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
If I manually copy a block, which is also marked as being part of a group, the new, copied block does not come thru as being part of that group, according to the LIST command.
But if I use the VBA object.copy method in code, the new, copied block seems to come thru as being part of that group, if I run the LIST command afterwards.
However, running a second VBA routine to remove the object from the group errors out.
Running yet another VBA routine to list the members of the group, VB does NOT report the new, copied block as being part of the group, yet the LIST command still does,
Is this a gremlin? can anyone else reproduce this behaviour? Ive attached a simple drawing, with a VBA Macro embedded inside.
Does anyone have a workaround? Im currently unable to remove the old group reference....
But if I use the VBA object.copy method in code, the new, copied block seems to come thru as being part of that group, if I run the LIST command afterwards.
However, running a second VBA routine to remove the object from the group errors out.
Running yet another VBA routine to list the members of the group, VB does NOT report the new, copied block as being part of the group, yet the LIST command still does,
Is this a gremlin? can anyone else reproduce this behaviour? Ive attached a simple drawing, with a VBA Macro embedded inside.
Does anyone have a workaround? Im currently unable to remove the old group reference....