I know how to clean them up, but what can I do in my work flow to avoid them?
I've been working on a 2 mile corridor and this is the 4th time they have corrupted my file
Joe Bouza
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Solved! Go to Solution.
Solved by Jeff_M. Go to Solution.
Solved by AlmasSuljevic. Go to Solution.
Hi Joe,
What does MOO stand for?
Are you referring to a Mask 0 error or?
Hi Joe,
*Warning* Multiply Owned Objects error means that multiple operations are trying to access the same objects at the same time which creates this conflict. I've seen it happening with styles. Please see this:
http://beingcivil.typepad.com/my_weblog/2010/08/warning-multiply-owned-objects.html
I hope it helps.
Hi Almas
I am familiar with the BC blog post on this. At this point I have already lost the assembly "visually" the construction tab still says they exist. Is there a way to get it back? Have you seen the files I sent in with the SR?
As for the multiple operations accessing the same object, this is confusing to me because the corridor file refs EG for the OML2 sub and several offset alignments to control tapers and widths. Thats it.
I'll go and begin version 5 but I fear Ill end up in the same place with the firs 4 versions each one ending the same way.
Here is another oddity. The assembly in the copy file from the day before that shows will not WBLOCK out or Clipboard yet the others do. So every version I do I have to remake the assembly. Not that big a deal but annoying.
Thanks
Joe
Joe Bouza
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
here is the wblock of tyhe assembly. Check the construction tab
Joe Bouza
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Joe Bouza
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Hi @Jeff_M and @AlmasSuljevic
Jeff, that was a great find. The good news I was able to reconstitute the assembly with the move subs command. The bad news, the corridor was whacked the subs were all crisscrossing and ignoring targets.
The good news: making a new assembly and copying the subs worked. I have my two mile corridor back with all the transitions in tact.
Almas, I think my MOO's was caused by me setting the OML2 sub in the assembly in layout mode defining the crown offset and overlay trim and then adding a alignment horizontal target to the corridor as I progressed. I'm not sure of that and would welcome your opinion back.
Thanks
Joe Bouza
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Can't find what you're looking for? Ask the community or share your knowledge.