Import XML to BDE Automatically
Working with legacy BDE databases like Paradox or dBASE? Advanced ETL Processor makes it easy to import structured XML into BDE data tables - no scripting, manual entry, or custom utilities required.
What Is BDE?
BDE (Borland Database Engine) is a legacy database engine developed by Borland for use with Delphi and C++Builder applications. It supports various formats including Paradox, dBASE, and FoxPro, and is commonly used in legacy business software.
While BDE is largely obsolete today, many desktop applications and industrial systems still rely on its database architecture. Advanced ETL Processor supports BDE natively, allowing you to automate XML-to-BDE workflows without rewriting old software.
Why Import XML into BDE?
- Feed external XML data into legacy Paradox or dBASE tables
- Automate data exchange for Delphi-based business apps
- Modernize workflows without replacing old systems
How to Import XML into BDE - Step-by-Step
1. Launch Advanced ETL Processor
Start the Enterprise Edition. Under Tools > Connections, configure:
- XML File connection (input)
- BDE connection (output) - use existing BDE aliases or file paths
2. Create a New Transformation
Right-click on a transformation group and select New to open a blank transformation canvas.
3. Configure XML Reader
- Drag the XML Reader onto the canvas if necessary
- Double-click to open Properties
- Select your XML file
- Select Table and Record XML Tags
4. Configure BDE Writer
- Drag the BDE Writer onto the canvas if necessary
- Double-click to open Properties
- Select your BDE alias or folder path and choose the target table
5. Map and Transform Fields
Use AutoMap or drag field links manually. You can:
- Convert text, numeric, and date values
- Trim, split, or concatenate strings
- Apply formulas and assign defaults
6. Run the Import
Click Execute to write XML content into your BDE data table. Use your Delphi app or BDE-compatible tools to review the result.
7. Automate and Monitor
- Use the built-in scheduler to automate XML imports
- Trigger processes on file arrival, schedule, or events
- Enable logs, rollback, and email notifications for errors
Where this import fits
Import XML to BDE is useful when XML 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 XML import workflows.
Business usage examples
Structured system feeds
Load XML exports into BDE with repeatable field mapping instead of hand-parsing nested records.
API and application integration
Import XML payloads into BDE so reports and downstream workflows can use relational data.
Scheduled XML processing
Validate XML files, route bad records, and write clean rows into BDE with clear logs.
Video Tutorial
FAQ
Can Advanced ETL Processor import XML to BDE?
Yes. Advanced ETL Processor can read XML, 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 XML import run on a schedule?
Yes. The package can run on a schedule, process matching XML 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.