Import Text to BDE Automatically
Looking to import data from Text to BDE?
Advanced ETL Processor Enterprise provides everything you need to automate the data import without writing custom scripts. Visually map and transform your fields, then run the Import immediately or schedule it to repeat automatically.
- 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
Video: Watch the Data Import in Action
Watch a general data-import walkthrough showing how to connect databases, map fields, and run an import in Advanced ETL Processor.
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.
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.
Automate Your Text-to-BDE Imports
Download the fully functional 30-day trial and build your first import using your own Text and BDE databases.
Direct download. No registration required.