VSys One: Volunteer Management Software

Table rebuild tool

NexusDB is unlike SQL Server in that it can be used in single-user standalone mode, with VSys writing directly to the database tables itself. Even when using NexusDB Server, NexusDB tables are more prone to file damage than those used by SQL Server. This tool provides a mechanism for verifying and repairing possibly damaged tables.

The first sign that something may be amiss with your tables would be an error like:
exception message: NexusDB: <unnamed TnxTable instance>: Read failure[$2401/9217]

Your first course of action is to call or e-mail technical support. We can read the error report and tell you which (if any table) has a problem. If this is not feasible due to time zone issues (or it's a weekend or holiday), you can follow the repair process yourself on all tables – no damage will occur if you repair an undamaged table.

Always make a backup of the underlying raw files (*.nx1 files) before using this tool. A backup made with VSys itself will not suffice if there is damage to the tables themselves since the VSys backup won't be able to read the complete tables. Have your IT people copy the *.nx1 files themselves.

Steps in this task

Get all other users out of VSys. This includes closing down VSys Lite, VSys Kiosk, VOXI and the Standalone E-mail Robot if you're using them. This tool can only be used if no other users have any tables open.
Back up your data. Do this by backing up the underlying *.nx1 files rather than the VSys One backup tool since that tool may not be able to capture all records from damaged tables.
Get to the database selection window and choose the database to work with. If VSys starts without prompting you for which database to use, hold down the left Ctrl key while VSys starts up. This will force VSys to prompt you for a database, allowing you to use this tool.
Click on the Tools link then select Verify and repair NexusDB tables in this database.
Select which tables to verify.
Click Rebuild. VSys will now check each table and report back the results of its progress.

SQL Server tables never need repairing.