Pervasive PSQL v10 SP3 - Pervasive Direct Access Components (PDAC) Readme
General Release - November 2009

Contents


The document contains the following topics:

About PDAC

Pervasive Direct Access Components (PDAC) are a set of Visual Component Library (VCL) components that allow direct access to Pervasive Database Engines from within the Borland Delphi and C++ Builder Environments. These components provide a replacement for the functionality of the Borland Database Engine (BDE). PDAC dramatically extends the database development options available to Delphi and C++ Builder developers.

The Pervasive Direct Access Components are provided in versions fully integrated with the following development environments:

System Requirements

Existing install of Pervasive PSQL v10 or Pervasive PSQL v10.30 database engine.

Getting Started

The runtime files for the PDAC access method are installed with the Pervasive PSQL engine by default.

The header files and sample files are available via Web download: PDAC: http://www.pervasive.com/developerzone/access_methods/pdac.asp.

Note  If you have an existing version of PDAC, you should uninstall it before installing the updated PDAC components. Otherwise, the PDAC installation will not succeed.

"Redist" Subdirectory

There is a "redist" directory for each Borland compiler. This directory contains the libraries that must be distributed with an application compiled with "Build with runtime packages."

Adding PDAC to C++ Builder's "Include" and "Library" paths

Although the PDAC libraries are installed into all Delphi and C++ Builder IDEs found on your system, it is necessary to set C++ Builder's "Project Options" to reflect the INCLUDE and LIBRARY paths for PDAC. These can be added to the default options, so the steps are unnecessary for every project using the Pervasive components.

To add Pervasive Direct Access Components to the INCLUDE and LIBRARY paths in C++ Builder:

  1. Select Project | Options, and choose the "Directories/Conditionals" tab.
  2. Add installdir\sdk\pdac\BCB?\include to the Include Path, where installdir represents the directory where you installed the SDK. Replace the ? with the version of C++ Builder you are using.
  3. Also add installdir\sdk\pdac\BCB?\lib and installdir\sdk\pdac\BCB?\lib\dcu to the Library Path, separated by a semicolon (;). Replace the ? with the version of C++ Builder you are using.
  4. Check the Default box (if you want these to be the defaults for all projects you create), then click OK to save these options.

After the Include and Library paths are set properly, use the Direct Access components exactly the same way as the corresponding Borland components.

Using the Samples with the PVideoDB Database

The PDAC samples reference a database named PVideoDB, which simulates the management of a video store. The PDAC download file includes the data files and dictionary files (DDFs) for PVideoDB, but you must create the database itself. The data files and DDFs are located in <directory>\samples\PvideoDB, where <directory> is the directory where you installed the PDAC header files and samples.

Use the following steps to create the PVideoDB database, which is required to use the PDAC samples.

  1. Start Pervasive PSQL Control Center from the Pervasive group in the Start menu.
  2. In Pervasive PSQL Explorer, expand the Engines node.
  3. Right-click on the desired server where the database engine is running.
  4. Click New > Database.
  5. Type "PVideoDB" for Database Name (and use it for the DSN name).
  6. Specify <directory>\samples\PVideoDB for Location.
  7. where <directory> is the location where you installed the header and sample files.

  8. Click Finish.
  9. Exit Pervasive PSQL Control Center.

Information on Additional Programs Included with PDAC

PDAC2IDE.exe

You install the PDAC SDK components by unzipping the components from an archive to a directory of your choice (installdir). PDAC2IDE.exe, installed in the installdir\PDAC directory, can be used to configure the Borland Delphi and C++ Builder Integrated Development Environments (IDEs) for the PDAC components.

You must run this utility manually after the PDAC SDK components are unzipped from their archive. PDAC2IDE can also be run if new IDEs are installed or if problems occur.

When installing, there is no need to uninstall first. Any old entries are automatically deleted prior to installation. Note that no files are deleted, copied, or installed; the program simply updates the IDEs for PDAC.

The command is used as follows:

To install PDAC to all Borland IDEs found on a system

pdac2ide

This will find all supported Borland environments and make the appropriate Registry entries for the components to appear on the Palette and be available for use.

To uninstall PDAC from all Borland IDEs found on a system

pdac2ide -u

To install or uninstall to/from specific IDEs

pdac2ide [-u] [D6] [D7] [C6]

One or more IDEs can be listed on the command line.

The -u parameter runs the uninstall only; if it is not given, PDAC will first be uninstalled, then re-installed into each listed IDE.

PDAC2IDE also accepts a -q parameter, for "quiet" mode, that does not write to the console; this is useful for inclusion in batch files.

FixBPR.exe

This is a utility to "fix" the C++ Builder .bpr (project) files. It replaces references to the old (original PDAC release> library names with the correct filenames for the new libraries. The original BPR file is saved as .bpr.old.

FixBPR is installed into the PDAC installation directory. It can be run from a DOS or CMD box as follows:

FixBPR  

This utility should be run against all C++ Builder projects developed using the original release of PDAC, so they will build with the correct libraries. It is only useful with projects developed with the earlier PDAC libraries; nothing is added to the BPR files if the old library names are not found. It is not necessary to run this utility on the "default.bpr" files located in the compilers' "bin" directories, as PDAC2IDE.exe performs that function during installation of PDAC.

Delphi 2007

Pervasive PSQL provides support for Delphi 2006 and Delphi 2007. Use the following steps to incorporate Delphi 2007 compatibility into your existing Delphi 2006 environment.

  1. Install Delphi 2007 into the same location as Delphi 2006 (BDS 2006).
  2. Add the packages and path information:
    • Components --> Install Packages --> Add. Select the design packages.
    • Add the paths to the Delphi compiled units (DCUs) and interface files (INTs).

Since Delphi 2007 is binary compatible with Delphi 2006, all of your existing Borland package libraries (BPLs) should work without any modification. Note that Delphi 2007 declares compiler variable VERSION_180 and VERSION_185.

Known Issues

The following are known issues with this release.

Tracking Number
Description
52067
Data not displayed for some PDAC properties in Delphi 2005 IDE.
The following properties display incorrectly:
TpvSession: servername
TpvDatabase: Aliasname
TpvTable: Database
TpvBatchmove: changetablename, KeyvoilTablename
pvsqlsession: servername
pvsqldatabase: Aliasname
Tpvquery: database
Tpvstoredprocedure: database
wwpvTable1: Database
wwpvquery: Database
wwpvstoreprocedure: Database
This issue does not occur when using Delphi 5, 6, or 7.
57363
PDAC does not support the BIGINT data type.
The BIGINT data type is an 8-byte integer. PDAC maps BIGINT to SQL_DECIMAL and manipulates data as SQL_C_CHAR type.

Technical Support

You may obtain technical support from the following Web-based support options:

Disclaimer

PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN "AS IS" BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THE ACCOMPANYING LICENSE AGREEMENT.

Copyright 2009 Pervasive Software Inc. All Rights Reserved.


Pervasive Software Inc.
http://www.pervasive.com
12365 Riata Trace Pkwy, Bldg B
Austin, TX 78727 USA
Voice: (512) 231-6000
Fax: (512) 231-6010
Online Pervasive Contacts

*** END OF README ***