Eliminate V7 problems that slow down project submittals.

By on

CLEARWATER, FL, USA — According to a survey we conducted in September 2004, over 74% of MicroStation users surveyed are using MicroStation J or earlier. Substantiating the survey results, Axiom receives many requests to handle new types of corruption found in design shops using V7. Knowing about these new types of corruption in V7 allows Axiom to enhance FileFixer and remain at the forefront of design file corruption repair and help MicroStation users meet deadlines without any snags.

Using Axiom’s time-saving software to assist while migrating to V8 is like having the best hand in a card game, you can’t lose!

MicroStation, despite being the most reliable CAD package in the world, sometimes needs a little help to cope with extraneous circumstances. A hardware problem, a network glitch, an untimely power failure or an error in your favorite in-house programmer’s latest MDL application can easily devastate an important design file. Further, there are other problems that come up like elements that can’t be deleted, elements that display oddly as you zoom in or out, or elements that just can’t be highlighted no matter how hard you try. The ability to handle all these issues is what has solidified FileFixer’s worth through the years.

Today, FileFixer stands alone as a preventive solution to MicroStation file corruption. The fact that FileFixer is unrivaled by another MDL application — with its swift speed of processing and unparalleled handling of design file corruption — makes it essential in today’s CAD culture. No MicroStation shop should operate without it.

Defaults handle 98.7% of reported corruption
With default settings, FileFixer handles 98.7% of all reported MicroStation V7 corruption. FileFixer can quickly fix common errors in multiple design files and cell libraries in the first run, leaving only esoteric or nested problems to be handled in a second run. But why does this happen? When FileFixer handles some types of common corruption, nested corruption problems emerge that were obscured by others. These nested types can be easily handled by changing problem-specific settings. FileFixer itself sometimes suggests changing default settings and trying another run.

End-of-file is still missing
FileFixer has the ability to fix “End-of-file missing” errors automatically. Originally MicroStation would display the “End-of-file missing, attempt repair?” dialog box — in later versions of MicroStation this was changed to “Unable to open design file. Please contact your local site administrator…”. If you had originally responded “Yes” to MicroStation’s request to repair the design file, you would most likely have made things worse. In this case, MicroStation “fixes” this problem by inserting an end-of-design marker (a flag that MicroStation uses to indicate the end of all the elements in the design file) before the first corrupted element it finds. If the end-of-design marker is inserted only 10% into the file, you would lose 90% of your work! FileFixer is able to fix this file corruption by scanning past the corrupted elements looking for the starting point of a chain of valid elements. FileFixer is able to salvage these healthy elements and properly place the end-of-design marker in the design file.

Eliminating phantom elements
Fixing “phantom elements” (elements that show up only in certain views or that appear only when zooming in or only show up in plots) is another common problem FileFixer fixes automatically. An incorrect range stored in the element will cause this problem. The range stored in the element has to include the exact geographic location of the element. When it doesn’t, you may not be able to select and modify it.

Planning to move to V8?
Making sure your V7 design file import into MicroStation V8 successfully is another popular concern. Some specific problems that arise when migrating your V7 design files to V8 are:

  1. Not all of the elements being copied to the V8 design file. This happens whenever the end-of-design marker is incorrectly placed in the V7 design file. FileFixer can automatically repair this corruption in the V7 file so that all of the elements are imported into the V8 design file.
  2. None of the graphical elements being displayed in MicroStation V8. FileFixer can repair the corrupted design file header element (first element in a design file which contains a lot of the information about the design file) that causes this problem by replacing it using FileFixer’s Repair Design File Header Elements feature.
  3. Not all the elements that make up a complex element (cell, connected line string, etc.) are being kept as part of the complex element. Some elements that make up the complex element may only be imported as simple elements in the V8 file. FileFixer can automatically repair this error in the V7 file so that the complex element is imported correctly into the V8 file.

Running out of time to run FileFixer?
Even though it is incredibly simple to run FileFixer on a set of files, some very busy CAD shops need an even simpler way. In these cases, you can set up FileFixer to run automatically every time a design file is closed or you can use the Windows™ Scheduler to set up FileFixer to search your directories for corrupt files every night. Set it and forget it, and never have another corrupt file sitting in your archives waiting for the disastrous day when you decide to open it.

See for Yourself...
Get FREE Trial Versions
* Select one or more of the following:
td>




Enter "AutoCAD" before submitting.