When you try to open Aspel SAE or SUA and see the message “Base de datos dañada” (Database corrupted), “Error al abrir tabla” (Error opening table), “Index is out of date”, or “Blob has been modified”, it means the Paradox database used by the program has become corrupted. This is one of the most frequent errors in Aspel and SUA, especially in environments with power outages or computers that shut down without properly closing the program. In this guide you will learn how to diagnose, repair, and prevent database corruption step by step.

The Error

The error messages can appear in several forms when trying to open a company or run a process in Aspel SAE or SUA:

  • “Base de datos dañada” — generic message that appears when trying to open Paradox database tables.
  • “Error al abrir tabla [table_name]” — indicates a specific table such as FACTURAS.DB, CLIENTES.DB, or MOV_ALMA.DB is corrupted.
  • “Index is out of date” — the index files (.PX, .XG, .YG) do not match the table data.
  • “Blob has been modified” — memo or BLOB fields in the table have lost integrity.
  • “Key violation” — duplicate records appear in primary keys due to index corruption.

These errors typically appear when starting the program, opening a company, generating reports, or invoicing. In the case of SUA, they usually occur when trying to generate the IMSS payment file or when querying employee records.

Root Cause

Aspel SAE and SUA use Paradox databases managed by the BDE (Borland Database Engine), a technology developed by Borland in the 1990s. These databases are particularly vulnerable to corruption for the following reasons:

  1. Power outages — If the computer shuts down while Aspel is writing data to a table, the index files are left in an inconsistent state with the data. This is the most common cause of corruption.

  2. Forced program closure — Using Task Manager to close Aspel or shutting down Windows without first closing the program leaves active lock files and can corrupt open tables.

  3. Network disconnections during writes — In multi-user environments where the database is on a shared server, if a workstation loses its network connection while writing data, the table can become corrupted for all users.

  4. Hard drive errors — Bad sectors on the disk where the Paradox .DB files are stored cause incorrect data reads.

  5. Incorrect BDE configuration — If the BDE NET DIR parameter is not properly configured in network environments, multiple computers may attempt to write simultaneously without coordination, corrupting the indexes.

  6. Antivirus scanning database files — Some antivirus programs temporarily lock .DB and .PX files during a scan, which can cause write errors if Aspel tries to access them at the same time.

Step-by-Step Solution

Step 1: Close all Aspel sessions

Before any repair, make sure no user has Aspel SAE or SUA open on any computer. If the database is on a network, check all connected workstations. Orphaned lock files (.LCK) should be deleted if they remain.

Step 2: Create a full backup

Copy the entire company folder to a safe location before attempting any repair:

C:\Program Files\Common Files\Aspel\Sistemas Aspel\SAE8.00\Empresas\Empresa01\

For SUA, the typical path is:

C:\Program Files\Sua\Datos\

Step 3: Delete index files

Navigate to the affected company folder and delete (do not rename) the following file types:

ExtensionFile typeAutomatically regenerated
.PXPrimary indexYes
.XGSecondary indexYes
.YGComposite secondary indexYes
.TVTable viewYes
.LCKLock fileYes
.VALValidationsYes

Important: Do not delete .DB (data) or .MB (memo fields) files — these contain your actual business data.

Step 4: Repair with Database Desktop

If deleting indexes does not resolve the issue, use Database Desktop (installed with BDE):

  1. Open Database Desktop from C:\Program Files\Common Files\Borland Shared\BDE\ or find it in the Start menu.
  2. Go to File > Open > Table and select the damaged table (for example, FACTURAS.DB).
  3. Change the type to Paradox if it is not already selected.
  4. If the table opens successfully, go to Table > Restructure.
  5. Without making any structural changes, click Save. This forces the reconstruction of all indexes.
  6. Repeat for each table that reports an error.

Step 5: Advanced repair with TUtility

For severe corruption where Database Desktop does not work, use TUtility (a Paradox table repair tool):

  1. Download TUtility from Aspel support sites or specialized forums.
  2. Run TUtility as administrator.
  3. Select Repair Table and navigate to the damaged table.
  4. TUtility will attempt to recover readable records and generate a repaired table.
  5. Replace the original table with the repaired one.

Alternative Solution

If the tools above cannot repair the database, there is a more aggressive manual method:

  1. Export readable data — Use Database Desktop to open each table that still works and export the data to CSV or DBF format.
  2. Create a new database — In Aspel SAE, create a new company from scratch.
  3. Import data — Use SAE import utilities to reimport catalogs (customers, suppliers, products).
  4. Restore from backup — If you have a recent backup, the fastest way is to restore it. Go to Utilerías > Respaldo/Restauración > Restaurar in SAE.

For SUA, if you have a backup file, you can restore it from Utilerías > Restaurar Respaldo. If no backup exists, you will need to re-enter transactions from the last submitted bimonthly period.

Prevention

Paradox database corruption is preventable in most cases by following these practices:

  • Install a UPS (Uninterruptible Power Supply) — Protect the computer and server from power outages. A 600VA UPS provides enough time to properly close Aspel before the battery runs out.
  • Always close Aspel before shutting down — Never turn off the computer with Aspel open. Close the program from its File > Exit menu.
  • Make daily backups — Configure automatic backups in SAE from Utilerías > Respaldo/Restauración. For SUA, manually back up the data folder at least once per week.
  • Configure BDE correctly — In BDE Administrator, ensure that NET DIR points to a shared network folder and all computers use the same path.
  • Exclude Aspel folders from antivirus scanning — Add SAE and SUA data folders as exceptions in your antivirus to prevent file locking during scans.
  • Consider migrating to SQL Server — Aspel SAE 8.0 supports Microsoft SQL Server as a database engine instead of Paradox, completely eliminating BDE corruption issues.
ErrorProbable causeQuick fix
”Table is busy”Orphaned .LCK fileDelete .LCK files from the data folder
”Could not find object”Table deleted or movedVerify all .DB files exist in the folder
”Invalid field name”Altered table structureRestructure table with Database Desktop
”Network initialization failed”BDE NET DIR misconfiguredCorrect NET DIR in BDE Administrator
”Insufficient memory”BDE SHAREDMEMSIZE too lowIncrease SHAREDMEMSIZE to 4096 in BDE Administrator

Summary

  • The “Database corrupted” error in Aspel SAE and SUA is caused by corruption of Paradox databases managed by BDE.
  • The main causes are power outages, forced shutdowns, and network disconnections during write operations.
  • The most effective solution is to delete index files (.PX, .XG, .YG) and let Aspel rebuild them.
  • For severe corruption, use Database Desktop or TUtility to repair tables.
  • Prevention: UPS, daily backups, proper program shutdown, and correct BDE configuration.
  • Long-term, consider migrating to SQL Server to eliminate Paradox-related issues.