<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Forward Merge in Project data &amp; BIM</title>
    <link>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130519#M7170</link>
    <description>As I understand it can reset the file overwriting /correcting settings that have become corrupt.&lt;BR /&gt;
&lt;BR /&gt;
There are some posts &lt;A href="http://archicad-talk.graphisoft.com/viewtopic.php?p=4893&amp;amp;highlight=forward+merge#4893" target="_blank"&gt;here&lt;/A&gt; and &lt;A href="http://archicad-talk.graphisoft.com/viewtopic.php?p=5199&amp;amp;highlight=forward+merge#5199" target="_blank"&gt;here&lt;/A&gt;</description>
    <pubDate>Sat, 24 Apr 2010 05:25:18 GMT</pubDate>
    <dc:creator>Erika Epstein</dc:creator>
    <dc:date>2010-04-24T05:25:18Z</dc:date>
    <item>
      <title>Forward Merge</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130516#M7167</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;I found a tech note on ArchicadWicki that describes one way &lt;BR /&gt;
to repair a damaged file. The note is as follows. &lt;BR /&gt;
 &lt;BR /&gt;
"Fixing corrupt files using file merging &lt;BR /&gt;
 &lt;BR /&gt;
This method is called Forward Merging and simply merges a new &amp;amp; reset file into the corrupt file. &lt;BR /&gt;
 &lt;BR /&gt;
   1. &lt;BR /&gt;
 &lt;BR /&gt;
      Create a New &amp;amp; Reset file in ArchiCAD &lt;BR /&gt;
   2. Delete all layers from this file and save it. (e.g. with name 'crashmerge.pln') &lt;BR /&gt;
   3. &lt;BR /&gt;
 &lt;BR /&gt;
      Open your corrupt file and select File-&amp;gt;Merge and select the crashmerge.pln file to merge. &lt;BR /&gt;
   4. Save your file  &lt;BR /&gt;
 &lt;BR /&gt;
Note: In case of you wish to merge a Teamwork file, please save your Teamwork files out to solo PLNs before doing this procedure and then re-share it afterward." &lt;BR /&gt;
 &lt;BR /&gt;
Many people on this forum have described the forward merge technique&lt;BR /&gt;
and all of them that I have read say the opposite of what the tech note says.&lt;BR /&gt;
They all say to merge the damaged file into the New and Reset file.&lt;BR /&gt;
To me, what these people say seems logical and what the tech note &lt;BR /&gt;
says is not.&lt;BR /&gt;
&lt;BR /&gt;
Anyone care to comment ?&lt;BR /&gt;
&lt;BR /&gt;
Thank you,&lt;BR /&gt;
Peter Devlin&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 30 May 2023 11:11:47 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130516#M7167</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-30T11:11:47Z</dc:date>
    </item>
    <item>
      <title>Re: Forward Merge</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130517#M7168</link>
      <description>The technote doesn't make sense to me either. In many cases the corrupt file won't open at all making the procedure impossible and I can't see any advantage to be had by merging a new, blank file into the damaged one.</description>
      <pubDate>Fri, 23 Apr 2010 21:55:43 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130517#M7168</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-04-23T21:55:43Z</dc:date>
    </item>
    <item>
      <title>Re: Forward Merge</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130518#M7169</link>
      <description>Hello Matthew,&lt;BR /&gt;
My thoughts exactly.&lt;BR /&gt;
Thanks for posting back.&lt;BR /&gt;
Peter Devlin</description>
      <pubDate>Fri, 23 Apr 2010 23:09:41 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130518#M7169</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-04-23T23:09:41Z</dc:date>
    </item>
    <item>
      <title>Re: Forward Merge</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130519#M7170</link>
      <description>As I understand it can reset the file overwriting /correcting settings that have become corrupt.&lt;BR /&gt;
&lt;BR /&gt;
There are some posts &lt;A href="http://archicad-talk.graphisoft.com/viewtopic.php?p=4893&amp;amp;highlight=forward+merge#4893" target="_blank"&gt;here&lt;/A&gt; and &lt;A href="http://archicad-talk.graphisoft.com/viewtopic.php?p=5199&amp;amp;highlight=forward+merge#5199" target="_blank"&gt;here&lt;/A&gt;</description>
      <pubDate>Sat, 24 Apr 2010 05:25:18 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130519#M7170</guid>
      <dc:creator>Erika Epstein</dc:creator>
      <dc:date>2010-04-24T05:25:18Z</dc:date>
    </item>
    <item>
      <title>Re: Forward Merge</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130520#M7171</link>
      <description>Hello Erika, &lt;BR /&gt;
Eric Batte's method is identical to the tech note method.&lt;BR /&gt;
I have never had a corrupt Archicad file so I am unable&lt;BR /&gt;
to find out which method, the tech note method or the method&lt;BR /&gt;
described by many people on the forum works. Maybe they both work.&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Peter Devlin</description>
      <pubDate>Sat, 24 Apr 2010 17:20:43 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130520#M7171</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-04-24T17:20:43Z</dc:date>
    </item>
    <item>
      <title>Re: Forward Merge</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130521#M7172</link>
      <description>Merging files can be a good way to repair them but on occation I have come across a corrupt file that can't be opened directly which would lead to the forward merge option Peter mentioned.&lt;BR /&gt;
But unless you are using identical templates you could end up with a whole bunch of nwanted layers, linetypes, wrong pen colours, etc.&lt;BR /&gt;
&lt;BR /&gt;
I have found that if a file can not be opened then simply opening another file, leaving it open and then opening the corrupt file is enought to get it open.&lt;BR /&gt;
Archicad will of course ask if you want to save the other file (which you don't).&lt;BR /&gt;
But having a file already open seems to reset the sticking point stopping the corrupt file from opening.&lt;BR /&gt;
And you don't have the problem of merging in a bunch of attributes you don't need.&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Tue, 27 Apr 2010 03:13:03 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130521#M7172</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2010-04-27T03:13:03Z</dc:date>
    </item>
    <item>
      <title>Re: Forward Merge</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130522#M7173</link>
      <description>&lt;BLOCKQUOTE&gt;Barry wrote:&lt;BR /&gt;But unless you are using identical templates you could end up with a whole bunch of nwanted layers, linetypes, wrong pen colours, etc.&lt;/BLOCKQUOTE&gt;

When attributes overlap during a merge, which one takes precedence - the &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;merger&lt;E&gt;&lt;/E&gt; or the &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;mergee&lt;E&gt;&lt;/E&gt;?&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;Barry wrote:&lt;BR /&gt;I have found that if a file can not be opened then simply opening another file, leaving it open and then opening the corrupt file is enought to get it open.&lt;/BLOCKQUOTE&gt;

This method should be added to the Wiki pages.</description>
      <pubDate>Tue, 27 Apr 2010 05:07:42 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130522#M7173</guid>
      <dc:creator>vistasp</dc:creator>
      <dc:date>2010-04-27T05:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: Forward Merge</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130523#M7174</link>
      <description>&lt;BLOCKQUOTE&gt;vistasp wrote:&lt;BR /&gt;
&lt;BR /&gt;
When attributes overlap during a merge, which one takes precedence - the &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;merger&lt;E&gt;&lt;/E&gt; or the &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;mergee&lt;E&gt;&lt;/E&gt;?&lt;BR /&gt;

&lt;/BLOCKQUOTE&gt;

My experience is that the attributes of the merged file are Appended.</description>
      <pubDate>Tue, 27 Apr 2010 06:46:25 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130523#M7174</guid>
      <dc:creator>Erika Epstein</dc:creator>
      <dc:date>2010-04-27T06:46:25Z</dc:date>
    </item>
    <item>
      <title>Re: Forward Merge</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130524#M7175</link>
      <description>&lt;BLOCKQUOTE&gt;vistasp wrote:&lt;BR /&gt;
When attributes overlap during a merge, which one takes precedence - the &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;merger&lt;E&gt;&lt;/E&gt; or the &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;mergee&lt;E&gt;&lt;/E&gt;?
&lt;/BLOCKQUOTE&gt;

The &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;merger&lt;E&gt;&lt;/E&gt; (parent file) will retain all of its attributes and only new ones with different index numbers will be added from the merged file.&lt;BR /&gt;
&lt;BR /&gt;
I guess that is another reason for the forward merge - so that your original attribute should remain unchanged although you may get new attributes.&lt;BR /&gt;
&lt;BR /&gt;
Merging your file into another default template will destroy all of the attributes unless they match exactly or have completely unique index numbers that are different from the file you are merging into.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
NOTE: the attributes are all matched by the index number (as seen in the attribute manager) and not by the names that we refer to them as.&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Tue, 27 Apr 2010 06:56:40 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130524#M7175</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2010-04-27T06:56:40Z</dc:date>
    </item>
    <item>
      <title>Re: Forward Merge</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130525#M7176</link>
      <description>All,&lt;BR /&gt;
&lt;BR /&gt;
Thank you for the tip on reversing the Wiki note recommendation.  Nice save in a tough spot.  I tried both ways, so I can tell you: merging the corrupt file into the blank file is what worked.&lt;BR /&gt;
&lt;BR /&gt;
I do have to relink the layouts to an internal source instead of the external (corrupt) source.  Is there a way around this?  That relinking bit is a drag.&lt;BR /&gt;
&lt;BR /&gt;
Tried something else - I went back to a copy of the corrupt file.  Removed a Hot Linked Module and that fixed my problem.  Hope this helps someone.  &lt;BR /&gt;
&lt;BR /&gt;
Snap</description>
      <pubDate>Mon, 13 Jun 2011 22:53:51 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Forward-Merge/m-p/130525#M7176</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2011-06-13T22:53:51Z</dc:date>
    </item>
  </channel>
</rss>

