The Sistema Único de Autodeterminación (SUA) from IMSS can show damaged or corrupt database errors at the most critical moments: when generating the monthly payment disk, when calculating bimonthly contributions, or simply when opening the program. This article explains how to diagnose the damage, repair the database using SUA’s built-in tool, and prevent the problem from recurring.

The Error

When the SUA database is damaged, the program may show one or more of these messages:

  • “Error accessing the database” — appears when opening SUA or querying employees
  • “Damaged table: [table name]” — indicates a specific table has corrupt records
  • “Corrupt index” — the search index is broken; SUA cannot locate records
  • “Cannot open the database” — complete failure when starting the system
  • “General access error” — a generic error that can have several underlying causes

These errors typically occur:

  • When opening SUA for the first time after a power outage or forced restart
  • When trying to generate the SUA-5 (payment disk) at the end of the month
  • When calculating bimonthly employer-employee contributions
  • When importing affiliation records from IDSE
  • When trying to make a backup from the utilities menu

Root Cause

The SUA database is based on Microsoft Access format (.mdb files). This format is susceptible to corruption when any of the following situations occur:

Immediate causes:

  • Power outage or forced shutdown while SUA was writing data
  • Closing the SUA window with the X button instead of using File → Exit
  • Windows operating system error that abruptly closes SUA
  • Virus or malware that modifies the database files

Cumulative causes:

  • Very large database that has not been compacted for months or years
  • Hard drive with bad sectors that SUA does not immediately detect
  • Multiple users opening SUA over a network without the correct multi-user module
  • Insufficient disk space during a data write operation

Installation causes:

  • SUA installed in a path with special characters (accents, spaces)
  • Insufficient Windows permissions on the data folder
  • Outdated SUA version with bugs fixed in later releases

Step-by-Step Solution

Follow these steps in order. Do not skip the initial backup — it is your safety net if something goes wrong.

Step 1 — Back up the current database

Before any intervention, copy the entire SUA folder to a safe location:

Typical data path: C:\SUA\DATOS\ or C:\IMSS\SUA\

Open Windows Explorer, navigate to that folder and copy it entirely to a USB drive or external disk. Even if the database is damaged, it may contain recoverable data you will need if the repair fails.

Step 2 — Close SUA on all networked workstations

If SUA is installed on a network, make sure no user has the program open. Even a single workstation with SUA active can prevent the repair or further damage the database during the process.

Step 3 — Launch SUA as Administrator

Right-click the SUA icon and select “Run as administrator”. Some repair processes require elevated permissions to modify the database files.

Step 4 — Access the repair utility

Inside SUA, go to the main menu:

Utilities → Repair database

In older versions of SUA, this option may appear as:

Tools → Verify integrity → Repair

Step 5 — Run the repair

Click the Repair or Start button. The process can take between 5 and 25 minutes depending on the size of your database and the disk speed. During this time:

  • Do not close SUA
  • Do not shut down the computer
  • Do not open other resource-intensive programs

Step 6 — Review the result

When finished, SUA will show a report with:

  • Number of tables reviewed
  • Tables successfully repaired
  • Tables with unrecoverable damage (if any)

If all tables show status “OK” or “Repaired”, close SUA and reopen it normally to confirm it works correctly.

Step 7 — Compact the database

After repairing, it is advisable to compact the database to free up space and improve performance:

Utilities → Compact database

Alternative Solution

If SUA’s built-in repair could not recover the database, you have two options:

Option A — Restore from a previous backup

If you have regular SUA backups, restore the most recent backup prior to the damage. See How to Restore a Backup in SUA IMSS for detailed instructions.

The basic process is:

  1. Go to Utilities → Restore backup
  2. Select the backup file (.zip or .bak generated by SUA)
  3. Confirm the restore
  4. Manually enter the records from the lost period

Option B — Repair with JetCompact (Microsoft)

Microsoft includes a tool called JetCompact (also known as CompactRepair) in Office/Access tools that can repair .mdb files directly:

  1. Download the Microsoft Access Database Engine Redistributable from Microsoft’s website
  2. Locate the SUA .mdb file (usually SUADAT.mdb or similar)
  3. Run JetCompact pointing to the damaged file
  4. Replace the original file with the repaired one

This option is more technical and should only be used if SUA’s built-in utility did not work.

Prevention

These habits prevent the SUA database from becoming corrupt again:

Automatic backups:

  • Configure SUA to back up automatically on close: Utilities → Backup configuration
  • Keep at least 3 recent backups in different locations (USB, network, cloud)
  • Make a manual backup before any bulk operation (importing records, generating disk)

Correct system use:

  • Always close SUA using the File → Exit menu, never with the window’s X button
  • Keep Windows updated — some patches fix .mdb file handling issues
  • Close SUA before shutting down the computer

Hardware:

  • Install a UPS (uninterruptible power supply) if power outages are frequent in your area
  • Check hard drive health periodically with tools like CrystalDiskInfo
  • Keep at least 10% free space on the disk where SUA is installed

Periodic maintenance:

  • Compact the database every 3 months: Utilities → Compact database
  • Verify integrity monthly from the utilities menu
  • Keep SUA updated to the latest IMSS version

If you continue having problems after repairing the database, check these related articles:

Summary

  • SUA database corruption is mainly caused by power outages, improper program closure, and lack of maintenance
  • Always back up the data folder before attempting any repair
  • SUA’s built-in utility (Utilities → Repair database) resolves most cases
  • If internal repair fails, restore from a previous backup or use Microsoft’s JetCompact
  • Prevent future damage with automatic backups, a UPS, and always closing SUA properly