You can open text and CSV files in Exportizer using these ways:

1. Opening through ODBC DSN (interface: ADO or BDE). Select ODBC data source option and then select the ODBC DSN from the drop-down list. But first, you should create an ODBC DSN of the corresponding type using Windows administrative tools, and point it to the folder which contains needed files.

2. Opening by specifying file name (interface: ADO or BDE). Select File option and then browse for the needed file.

3. Opening by specifying folder name (interface: ADO or BDE). Select Folder option, select a driver from the drop-down list, and then browse for the folder with needed files.

4. Opening through connection string (interface: ADO). Select Connection string option and write a connection string. This way is the most flexible one because it allows to specify many additional parameters of the database connection. It is recommended for advanced users. Here are basic connection strings (more examples and details can be found in the Internet):

Provider=Microsoft.Jet.OLEDB.4.0;TEXT;DATABASE=C:\MyCSVFolder;   (32 bit)

Provider=MSDASQL.1;Extended Properties="DefaultDir=C:\MyCSVFolder;Driver={Microsoft Text Driver (*.txt; *.csv)};DriverId=27;Extensions=asc,csv,tab,txt;"

Driver={Microsoft Text Driver (*.txt; *.csv)};Dbq=C:\MyCSVFolder;Extensions=asc,csv,tab,txt;   (32 bit)

Driver=Microsoft Access Text Driver (*.txt, *.csv);Dbq=C:\MyCSVFolder; Extensions=asc,csv,tab,txt;   (64 bit)

The first connection string is recommended when opening text files in Unicode encoding (in the 32-bit environment).
If you have problems with opening text or CSV file in Exportizer or its field structure is not as you expected, it probably means that the file does not have a schema describing its field structure or the schema was incorrectly defined.
The application bitness (32 or 64) must match with the bitness of the used third-party components (ODBC drivers, OLEDB providers etc).

See also

Connection Strings Examples