User’s Guide – FileFixer for V8

Chapter 1 — Introduction

The Tradition Continues

Since 1987 Axiom has provided the Intergraph and (later) the MicroStation communities with independent and objective file analysis and repair. By popular demand, this tradition continues with FileFixer for V8.

It is not Axiom’s position that any version of MicroStation introduces erroneous data into design files. MicroStation/J is quite robust. Nevertheless, our V7 clients still regularly report design file problems to us and use FileFixer regularly. How can this be?

Even if MicroStation (V7 or V8) never introduced any erroneous data into design files, factors beyond Bentley’s control can still impact your files: acts of God, acts of Bill Gates, your operating system, your network software, your network hardware, your server, your CPU, your hard drives and your electric power company.

And sure enough, the tradition continues with MicroStation V8.

FileFixer for V7 is the best guarantee that your V7 files will import into V8 healthy and whole.

Once you begin production with MicroStation V8, you enter the realm of FileFixer for V8.

Like its V7 counterpart, FileFixer for V8 will evolve in response to client requests. The “New Features and Fixes” section of this guide chronicles the evolution of FileFixer for V8.

We look forward to hearing from you about FileFixer for V8.

To get started immediately, see the Quick Start.

Features and Benefits

  • Fixes V8 design files and cell libraries at the touch of a button
  • Fixes 2D and 3D MicroStation files in batch
  • Fixes internal structured storage problems
  • Processes models automatically
  • Identifies and repairs structured storage (compound file) problems (new for V8)
  • Generates complete reports of the anomalies found and the actions done to fix them
  • Includes the most-used features from the V7 version of FileFixer

Note: See the “New Features and Fixes” section of this guide for a complete description of the latest FileFixer enhancements.

Urgent note

It is important to create a backup copy of a design file before repairing it with FileFixer.

There are two reasons for this.

  1. If anything non-optimal is later discovered about the fixed file, you will still have the original file to work with. Although FileFixer generally does a good job of repairing design files, the user is still the final judge as to whether the “fixed” file is truly superior to the original file.
  2. If you need assistance with design file repair, Axiom Support personnel will need a copy of the original unfixed design file.