Database files (*.mdb, *.dbf, *.csv)

Indexing desktop database formats such as Access, XBase, and CSV.

The dtSearch Engine uses internal file parsers to index XBase, CSV, Access, and XML data.

Database Records

The naming convention for the records is based on the File Parser API for items contained in a container. Example:

     c:\docs\sample.mdb>1cf|sample.customer#128

The following explains the components of this filename:

Component	Meaning
c:\docs\sample.mdb	Path and filename of the database
>	Delimiter used in the File Parser API to separate the filename and subitem of a document stored inside a container.
1cf	Hex ordinal identifying the subitem (can be ignored)
\|	Delimiter used in the File Parser API to separate the ordinal and name components of an item stored inside a container.
Customer#128	Name of the table and row identifier

The row identifier for a row is generated by each file parser in a different way according to the requirements of that format. For example, for CSV data the row identifier includes the byte offset of the start of the row.

ODBC

dtSearch versions prior to 7.54 relied on ODBC and an external file parser, dtv_odbc.dll, to parse Microsoft Access (*.mdb) databases. This is no longer required unless you are indexing data created with Microsoft Access versions prior to 1995. To enable ODBC database indexing, put dtv_odbc.dll in a subdirectory named "viewers" of the dtSearch Engine's "Home" directory, which is usually the directory where dten600.dll is located.