<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MicroStation Tips &#187; missing elements</title>
	<atom:link href="http://microstationtips.com/tag/missing-elements/feed/" rel="self" type="application/rss+xml" />
	<link>http://microstationtips.com</link>
	<description>Time-saving MicroStation Tips and Tricks</description>
	<lastBuildDate>Tue, 27 Dec 2011 14:09:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Recover Missing Elements from Your MicroStation Files</title>
		<link>http://microstationtips.com/recover-missing-elements-from-your-microstation-files/</link>
		<comments>http://microstationtips.com/recover-missing-elements-from-your-microstation-files/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 17:15:03 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Element Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[Eiren Smith]]></category>
		<category><![CDATA[FileFixer]]></category>
		<category><![CDATA[missing elements]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=111</guid>
		<description><![CDATA[By Eiren Smith, Axiom’s Vice President for Technology &#8211; www.AxiomInt.com Has this ever happened to you? You’ve been working on a design file for weeks. You’ve filled it with elements to your heart’s content. One fine morning, you load the file in MicroStation, and your eyes open wide in dismay. Hundreds of elements are missing [...]]]></description>
			<content:encoded><![CDATA[<p class="body"><span class="bodyHeader2">By Eiren Smith,                              Axiom’s Vice President for Technology &#8211; </span><a href="http://www.axiomint.com/"><span class="bodyHeader2">www.AxiomInt.com</span></a></p>
<p class="body">Has this ever happened to you?                              You’ve been working on a design file for weeks.                              You’ve filled it with elements to your heart’s                              content. One fine morning, you load the file in MicroStation,                              and your eyes open wide in dismay. Hundreds of elements                              are missing from your design! What happened? Your                              design file fell pray to file corruption.</p>
<p class="body">What you may not know is there’s                              a good chance that your elements are still in the                              design file. How could this be? To explain, let us                              take a small excursion. Think of a design file as                              a gigantic skyscraper; think of each floor of the                              skyscraper as a MicroStation element; and think of                              MicroStation itself as an elevator. To arrive at the                              bottom floor from the top floor of the skyscraper,                              an elevator has to first pass through each floor in                              between. MicroStation opens a design file in a similar                              fashion. To open a design file, MicroStation first                              scans the file from the top floor (in other words,                              from the first element in the file) all the way to                              the bottom floor (to the last element in the file).                              Just like an elevator would expect to find the bottom                              floor at the bottom of a skyscraper, MicroStation                              expects to find an “end-of-design marker”                              at the bottom of a design file. Simply put, the end-of-design                              marker tells MicroStation that the end of the file                              has been reached and that there aren’t any more                              elements to display. For various reasons (network                              glitches, hardware malfunctions, application errors                              and more), an erroneous “end-of-design marker”                              can wind up in the design file somewhere other than                              at the actual end of the file. The result: all elements                              after the erroneously placed end-of-design marker                              are no longer recognized or displayed by MicroStation!</p>
<p class="body">The easiest and safest way                              to bring back your missing elements is by using Axiom’s                             <em> FileFixer</em> &#8211; the utility that lets you fix any MicroStation                              file automatically!</p>
<p class="body">In this technical bulletin,                              I’ll show you how to set up <em>FileFixer</em> to recover                              elements that lie past an erroneous end-of-design                              file marker.</p>
<ol>
<li><span class="body"> Select <em>FileFixer </em>from                                the Axiom menu [located on the MicroStation menu                                bar].</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_01.gif" alt="" width="197" height="167" /></li>
<li> <span class="body"><em>FileFixer’s</em> main                                dialog box shows up. Make sure the repair “Mode”                                pull-down menu is set to “Automatic Design                                File Repair”.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_02.gif" alt="" width="251" height="22" /></li>
<li><span class="body"> Next, click on the &lt;Edit                                List&gt; button to select the MicroStation file                                that is missing elements. For the purposes of this                                article, we created and selected the file “eod-marker.dgn”.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_03.gif" alt="" width="431" height="22" /></li>
<li> <span class="body">Then, on the <em>FileFixer </em> menu bar, choose the “Options” menu and                                then choose “Repair”.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_04.gif" alt="" width="165" height="134" /></li>
<li> <span class="body">Once in the “Repair                                Options” dialog box, select the “Element”                                category.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_05.gif" alt="" width="219" height="186" /></li>
<li><span class="body"> Having selected the “Element”                                category, check the option “Recover elements                                past the end-of-design marker”. Click &lt;OK&gt;                                afterwards.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_06.gif" alt="" width="454" height="185" /></li>
<li><span class="body"> Back in <em>FileFixer’s </em> main dialog box, click &lt;Start&gt; to recover                                all the missing elements automatically.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_07.gif" alt="" width="101" height="24" /></li>
<li> <span class="body">After processing the design                                file, <em>FileFixer</em> prompts you to click the &lt;OK&gt;                                button. Notice that the dialog box states “Repaired                                files have .fix extension”. This is because                                <em>FileFixer</em> repairs a copy of your design file by                                default. This is a precaution to protect you in                                the unlikely event that the repair produces results                                that are less than perfect. You’ll always have                                the original file to go back to!</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_08.gif" alt="" width="333" height="166" /></li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/recover-missing-elements-from-your-microstation-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

