Import Excel to BDE Automatically
If you're still maintaining systems that use the Borland Database Engine (BDE), you may need to load Excel data into legacy Paradox or dBase tables. Advanced ETL Processor Enterprise offers a no-code, automation-ready solution to import Excel into BDE-compatible data sources - no scripts, macros, or manual intervention required.
What Is BDE?
The Borland Database Engine (BDE) was once the default data access layer for Borland Delphi and C++ Builder applications. Though now considered legacy, many internal systems still rely on BDE to access Paradox, dBase, and other file-based databases. Automating Excel-to-BDE imports ensures continued system compatibility and stability.
Step-by-Step: Import Excel into BDE
- Open Advanced ETL Processor Enterprise
- Create a BDE connection by selecting the appropriate alias or path to your Paradox or dBase tables.
- Create a Directory connection to your Excel source folder.
- Create a new Transformation:
- Right-click on a Transformation group and choose New
- Delete the default Validator object to simplify the workspace.
- Configure the Data Reader:
- Select your Excel file (.xls or .xlsx)
- Choose a worksheet, range, or Excel table
- Use masks like
*.xlsxto support batch processing
No need to preprocess Excel files - the tool supports reading dynamic file names and multiple sheets.
- Set Up the Data Writer:
- Select your BDE connection
- Point to the target table or create one if needed
- Map Fields:
- Open the Transformer object
- Use drag-and-drop or AutoMap to match Excel columns with BDE fields
- Apply transformations for trimming, formatting, and data type conversion
- Run and Verify:
- Click Execute to run the import
- Review logs for success status and row counts
- Automate If Required:
- Set up time-based scheduling
- Use triggers based on file changes or external signals
Who Is This For?
This workflow is ideal for organizations maintaining Delphi or C++Builder applications that rely on Paradox or dBase. Automating Excel data loading helps reduce legacy tech risks and saves hours of manual work.
Where this import fits
Import Excel to BDE is useful when Excel data needs to feed BDE, reporting databases, operational systems, migration jobs, or downstream ETL workflows. Use it when the same import needs validation, mapping, transformations, scheduling, and logs instead of another manual load.
Do not automate the import until the source layout, target table, key fields, write mode, and failure behaviour are agreed. Automation repeats rules; it does not rescue unclear ones.
Useful links for this import
Start with the Advanced ETL Processor Enterprise overview, then download the fully functional 30-day trial. The import-data hub lists the other Excel import workflows.
Business usage examples
Legacy Borland systems
Load Excel extracts into a BDE-backed application while keeping the old system running and the import process repeatable.
Operations data entry
Import product, customer, or order spreadsheets into BDE tables with mapping and logs instead of retyping rows by hand.
Migration preparation
Stage Excel data in BDE during a phased migration so legacy users can keep working while newer databases are prepared.
Watch the Tool in Action
FAQ
Can Advanced ETL Processor import Excel to BDE?
Yes. Advanced ETL Processor can read Excel, map fields, validate data, write to BDE, and log the import.
Do I need to write scripts for the import?
No scripting is required for the normal import workflow. You can configure the reader, writer, mapping, validation, and schedule visually.
Can the Excel import run on a schedule?
Yes. The package can run on a schedule, process matching Excel files, archive originals, and write rows to BDE with the same validation rules each time.
Can imported data be transformed before loading?
Yes. You can clean values, convert data types, calculate fields, split columns, and apply lookup rules before writing to the target.
Can bad rows be logged or rejected?
Yes. Add validation rules so rejected rows, failed files, row counts, and error details are visible after each run.
What should I check before the first production import?
Check source layout, target table, key fields, data types, date formats, write mode, archive folder, and failure handling.
When should I not automate the import yet?
Do not automate it until the source layout, target table, key fields, and bad-row handling are clear. Automation repeats rules; it does not invent them.
Can I test the import before buying?
Yes. Download the fully functional 30-day trial, build one small import, and test it with a deliberately awkward sample file.
Stop struggling with fragile ETL scripts. Start shipping reliable workflows.
Download the fully functional 30-day trial. Build your first automation in 10 minutes or less.
Direct link, no registration required.