Documentation
Home Evaluation Summary for programmers Product limitations Goals of Axisbase Quick start Installation Using the launchpad and opening databases Connecting to a sample database Using building blocks Planning Define the purpose Define the requirements Borrow existing work Determine the architecture Design the data model Design the process model Deploy and maintain the product
Tutorials
building blocks
Performing a mailmerge Bulk e-mailing
Programming
Single-threaded progress indicator in c#
Reference
Database menu items
Import XML Save Copy As Integrity Check Change Password
Database Properties window
Opening the database properties window Record types tab Display types tab Roles and Users tabs Sidebar tab Database ID/Links tab Counters tab
Building blocks
Building blocks window Editing grids and cells Hyperlinks and nesting Data Subset window Data Outsource window List window Window window Report window Bulk Operation window Label Printer window Choosing a data source
Special topics
Expression syntax Browse records Storing building blocks within other building blocks Programming Using custom code in building blocks Using Axisbase as an embedded database Axis1.Util namespace reference Axis1.Data namespace reference (Fishnets) Axis1.Data namespace reference (other) Axis1.Forms namespace reference

Integrity Check

The Integrity Check command is available from the Database menu, but only if you opened a file locally; it is not available if you connected to a server database.

File corruption may occur if the power is suddenly cut off while Axisbase is writing to the database file, or hardware failure. When Axisbase detects corruption, it reports messages, which may be viewed in the Integrity Check window. One instance of corruption can lead to further messages at a later time. If the menu item is highlighted, there are messages waiting to be read. Unread messages are not saved when the file is closed.

In addition to messages, the Integrity Check command offers tools which can be used to diagnose or correct corruption.

If you suspect corruption or there are messages indicating corruption:

  1. Choose the Save Copy As command to save a copy of the database to a new file. Don't overwrite any backups.

  2. Run all of the integrity tools

Although the Integrity Check command is not available in server mode, you can check the directory where the database is stored for files starting with the name of your database file, and ending with "errors.txt". Any errors detected by the server are written to this file.

(c) 2014-2015 Divergent Labs, Inc.