Import Text to BDE Automatically
Still using legacy applications based on the Borland Database Engine (BDE)? Advanced ETL Processor makes it easy to import CSV, tab-delimited, or fixed-width text files into BDE-managed databases without writing any code. Whether you're working with Paradox, dBASE, or other BDE formats, our solution helps you modernize your data integration process with automation and reliability.
What Is BDE?
BDE (Borland Database Engine) is a legacy data access framework used primarily by Delphi and C++Builder applications. It supports older file-based databases such as Paradox and dBASE and is still used in many long-running desktop and enterprise systems that haven't transitioned to newer platforms.
Why Use Advanced ETL Processor?
- No scripting or programming required
- Compatible with Paradox, dBASE, and other BDE drivers
- Supports CSV, tab-delimited, and fixed-width text formats
- Visual drag-and-drop field mapping and transformation
- Automated execution, logging, and scheduling
How to Import Text Files into BDE
- Open Advanced ETL Processor
- Create a Directory Connection
Link to the folder where your text files are stored. - Set Up a BDE Connection
Define the BDE alias or physical file path (e.g., to a `.DB` or `.DBF` file) using the BDE driver. - Create a New Transformation
- Right-click on the transformation group and choose New
- Configure the Text File Reader
- Use masks like
*.csv,*.txt - Choose delimiters, encoding, and whether to use headers
- Use masks like
- Configure the BDE Writer
- Select your BDE connection
- Choose the table or DB file for data insertion
- Specify insert or update operations
- Map Fields and Transform
- Drag-and-drop source fields to target columns
- Apply type conversions, trimming, or formulas if needed
- Run the Import
- Click Execute to process data
- Review logs for errors, row counts, and completion status
- Schedule and Automate
- Set up a schedule (hourly, daily, etc.)
- Trigger based on file presence or external events
Supported Text Formats
- CSV (comma-separated values)
- Tab-delimited text
- Fixed-width files
- Custom delimiter formats
Ideal For
- Organizations maintaining legacy Delphi applications
- Paradox or dBASE file imports
- Back-office or industrial control systems using BDE
Where this import fits
Import Text to BDE is useful when Text 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 Text import workflows.
Business usage examples
Partner file feeds
Load recurring CSV or delimited text files into BDE after checking required fields, dates, and numeric values.
Log and export processing
Import text exports into BDE so analysts can query structured rows instead of opening another flat file.
Operational batch imports
Schedule text-to-BDE imports with archive folders, rejected rows, and run logs for safer reruns.
Watch It in Action
FAQ
Can Advanced ETL Processor import Text to BDE?
Yes. Advanced ETL Processor can read Text, 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 Text import run on a schedule?
Yes. The package can run on a schedule, process matching Text 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.