User`s guide

A.2.4.2 dBASE, FoxPro, Clipper
Crystal Reports has been designed to open dBASE data simply and directly through the xBase engine
(inside crdb_p2bxbse.dll). FoxPro and Clipper are dBASE compatible database formats, and Crystal
Reports uses the same DLL to access files created by any of these three DBMS applications.
Note:
The crdb_p2bxbse.dll translation layer supports FoxPro files up through version 2.6. See Visual FoxPro
for versions after 2.6.
The file crdb_p2bxbse.dll handles all translation between Crystal Reports and the dBASE, FoxPro, or
Clipper files. Each database file contains only a single database table, but there is no limit to the number
of files that can be accessed by a report.
Note:
dBASE data can also be accessed through the Borland Database Engine (BDE) using the translation
file crdb_p2bbde.dll. To see how the BDE communicates with database data, see Paradox. The BDE,
however, does not support FoxPro or Clipper data.
A.2.4.3 Paradox
Files created with Paradox (.DB) are made available to other applications through the Borland Database
Engine (BDE). The BDE does the actual work with the Paradox data, retrieving the requested tables
and fields. Since the BDE works so closely with the actual data, it combines with the Paradox database
file to create the database layer in the three layer data access model. Crystal Reports accesses the
BDE through the crdb_p2bbde.dll translation file.
Note:
Crystal Reports does not install the BDE. It must be installed separately from a third-party application.
A.2.4.4 DAO
Microsoft's Data Access Object (DAO) Engine for versions of Access 2.0 and later is the part of the
Microsoft Access Database Management System that actually handles your database data. As a user,
you usually do not work directly with the DAO engine. It acts as a gateway through which Access data
is made available to applications. Since the DAO engine is so closely tied to Access data, Crystal
Reports considers it a part of the actual database.
2012-03-14647
Accessing Data Sources