Library > Products > Pervasive.SQL > Pervasive.SQL 9.1 > PDAC Programmer's Guide > Using Direct Access Components > Deploying an Application Based on PDAC

PreviousPDAC Programmer's Guide (9.1 revision 1) Next

Deploying an Application Based on PDAC

Show this topic in Library frames

With a few variations regarding the Borland and other runtime libraries, there are two basic ways to build PDAC applications for deployment to end users: using "runtime packages" or statically linking the PDAC libraries into the application's executable file. C++ Builder also offers the option of dynamically or statically linking the Borland runtime library.

Note
The SDK-supplied file DRM.DLL (from the \PVSW\BIN directory after an SDK installation) must be installed into the path in all deployment configurations, and either a Pervasive.SQL V8 client or a Pervasive.SQL engine (Server or Workgroup) must be properly installed on the target computer for a PDAC application to run.

Deciding whether to Use Runtime Packages

Using runtime packages has several advantages. It provides the smallest executable possible; this can be important where the executable or updates must be downloaded or transferred over slow links. This option allows sharing of the PDAC and Borland runtime binaries; this can save considerable disk space and memory in environments with many Borland and PDAC applications.

A disadvantage is that more files must be distributed and kept current, and the shared files can be vulnerable to third party installations that install incorrect versions of them in shared subdirectories. If runtime packages are not used, only the application and DRM.DLL must be deployed; the PDAC libraries are statically linked into the executable, which will be correspondingly larger.

To use runtime packages, the developer must deploy both the application's executable and the appropriate PDAC libraries (from the "redist" subdirectories in the PDAC installation directories), as well as any Borland or other runtime libraries (borlndmm.dll, found in the compiler's "bin" directory, is often needed).

Redist Subdirectory

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

Note
Each redist directory also includes .DCP or .BCP files that are not redistributable except within the licensee's organization to allow development with derived classes. These files may not be distributed outside the licensee's organization; only the .DPL and .BPL packages may be distributed with applications.

IDS Deployment

PDAC applications cannot be used with the I*net Data Server.

Deployment Instructions for PDAC

Select from the following instructions based on the development environment that you use:

Building and Deployment Instructions for C++ Builder 5

In the C++ Builder IDE, set the appropriate options as follows:

  1. From the Menu, select Project | Options
  2. Select the Linker tab.

    3. To have the application dynamically link the Borland runtime library, make sure "Use dynamic RTL" is checked. If you want to statically link the runtime library into the application's executable, make sure the option is unchecked.

  3. Click the Packages tab.

    4. To have the application dynamically link with the PDAC libraries at runtime, make sure "Build with runtime packages" is checked, and add the appropriate PDAC packages to the edit box's list, as follows:

    [If the PDAC packages were added to the Build list at installation, this step is not necessary.]

    If the application uses the components on the left column of the following table, the packages (.BPI FILES) from the right column must appear in the build list.

    Components Used
    Packages
    [Transactional]
    TPvSession,
    TPvDatabase,
    TPvTable,
    TPvBatchMove
    PvCommonB5, BtvDirectB5
    TwwPvTable
    PvCommonB5, BtvDirect_ipB5
    [Relational]
    TPvSQLSession,
    TPvSQLDatabase,
    TPvQuery,
    TPvUpdateSQL,
    TPvSQLStoredProc
    PvCommonB5, SQLDirectB5
    TwwPvQuery,
    TwwPvSQLStoredProc
    PvCommonB5, SQLDirect_ipB5

    To select packages, click Add, then Browse, and select the packages from the \PVSW\SDK\PDAC\BCB5\LIB directory (for a default installation). All the packages may be selected at once.

    Note
    If the PDAC packages are not added to the list, they will be compiled into the executable and the shared libraries will not be used, even if the box is checked.

To statically link the PDAC libraries into the application's executable, make sure "Build with runtime packages" is unchecked.

If "Build with runtime packages" is checked at compile time, the following libraries must be installed when the application is deployed, in addition to the application itself, drm.dll, and any other packages or DLLs it requires:

From \PVSW\SDK\PDAC\BCB5\REDIST, if their respective .BPI files are in the package build list: 

PvCommonB5.bpl 
BtvDirectB5.bpl 
BtvDirect_ipB5.bpl 
SQLDirectB5.bpl 
SQLDirect_ipB5.bpl

These files may be installed in the same subdirectory as the application's executable, but Pervasive recommends placing them in the target machine's path so they may be shared by other applications. The directory \PVSW\BIN is a good choice, on computers where it is the primary Pervasive executable directory.

In addition, the C++ Builder - PDAC application will require an installation of either a Pervasive.SQL V8 engine (Server, Workgroup, or Workstation) or a Pervasive.SQL V8 client and a remote server appropriately installed and configured.

Building and Deployment Instructions for C++ Builder 6

In the C++ Builder IDE, set the appropriate options as follows:

  1. From the Menu, select Project | Options
  2. Select the Linker tab.

    3. To have the application dynamically link the Borland runtime library, make sure "Use dynamic RTL" is checked. If you want to statically link the runtime library into the application's executable, make sure the option is unchecked.

  3. Click the Packages tab.

    4. To have the application dynamically link with the PDAC libraries at runtime, make sure "Build with runtime packages" is checked, and add the appropriate PDAC packages to the edit box's list, as follows:

    [If the PDAC packages were added to the Build list at installation, this step is not necessary.]

    If the application uses the components on the left column of the following table, the packages (.BPI FILES) from the right column must appear in the build list.

    Components Used
    Packages
    [Transactional]
    TPvSession,
    TPvDatabase,
    TPvTable,
    TPvBatchMove,
    TwwPvTable
    pc200r65, pb200r65
    [Relational]
    TPvSQLSession,
    TPvSQLDatabase,
    TPvQuery,
    TPvUpdateSQL,
    TPvSQLStoredProc,
    TwwPvQuery,
    TwwPvSQLStoredProc
    pc200r65, ps200r65

    To select packages, click Add, then Browse, and select the packages from the \PVSW\SDK\PDAC\BCB6\LIB directory (for a default installation). All the packages may be selected at once.

    Note
    If the PDAC packages are not added to the list, they will be compiled into the executable and the shared libraries will not be used, even if the box is checked.

To statically link the PDAC libraries into the application's executable, make sure "Build with runtime packages" is unchecked.

If "Build with runtime packages" is checked at compile time, the following libraries must be installed when the application is deployed, in addition to the application itself, drm.dll, and any other packages or DLLs it requires:

From \PVSW\SDK\PDAC\BCB6\REDIST, if their respective .BPI files are in the package build list: 

pc200r65.bpl 
pb200r65.bpl 
ps200r65.bpl

These files may be installed in the same subdirectory as the application's executable, but Pervasive recommends placing them in the target machine's path so they may be shared by other applications. The directory \PVSW\BIN is a good choice, on computers where it is the primary Pervasive executable directory.

In addition, the C++ Builder - PDAC application will require an installation of either a Pervasive.SQL V8 engine (Server or Workgroup) or a Pervasive.SQL V8 client and a remote server appropriately installed and configured.

Building and Deployment Instructions for Delphi 5

In the Delphi IDE, set the appropriate options as follows:

  1. From the Menu, select Project | Options
  2. Select the Packages tab.

    3. To have the application dynamically link with the PDAC libraries at runtime, make sure "Build with runtime packages" is checked, and add the appropriate PDAC packages to the edit box's list, as follows:

    [If the PDAC packages were added to the Build list at installation, this step is not necessary.]

    If the application uses the components on the left column of the following table, the packages (.DCP FILES) from the right column must appear in the build list.

    Components Used
    Packages Required
    [Transactional]
    TPvSession,
    TPvDatabase,
    TPvTable,
    TPvBatchMove
    PvCommonD5, BtvDirectD5
    TwwPvTable
    PvCommonD5, BtvDirect_ipD5
    [Relational]
    TPvSQLSession,
    TPvSQLDatabase,
    TPvQuery,
    TPvUpdateSQL,
    TPvSQLStoredProc
    PvCommonD5, SQLDirectD5
    TwwPvQuery,
    TwwPvSQLStoredProc
    PvCommonD5, SQLDirect_ipD5

    To select packages, click Add, then Browse, and select the packages from the \PVSW\SDK\PDAC\Delphi5\LIB directory (for a default installation). All the packages may be selected at once.

    Note
    If the PDAC packages are not added to the list, they will be compiled into the executable and the shared libraries will not be used, even if the box is checked.

To statically link the PDAC libraries into the application's executable, make sure "Build with runtime packages" is unchecked.

If "Build with runtime packages" is checked at compile time, the following libraries must be installed when the application is deployed, in addition to the application itself, drm.dll, and any other packages or DLLs it requires:

From \PVSW\SDK\PDAC\Delphi5\REDIST, if their respective .DCP files are in the package build list: 

PvCommonD5.bpl 
BtvDirectD5.bpl 
BtvDirect_ipD5.bpl 
SQLDirectD5.bpl 
SQLDirect_ipD5.bpl

These files may be installed in the same subdirectory as the application's executable, but Pervasive recommends placing them in the target machine's path so they may be shared by other applications. The directory \PVSW\BIN is a good choice, on computers where it is the primary Pervasive executable directory.

In addition, the Delphi - PDAC application will require an installation of either a Pervasive.SQL V8 engine (Server or Workgroup) or a Pervasive.SQL V8 client and a remote server appropriately installed and configured.

Building and Deployment Instructions for Delphi 6

Starting with Delphi 6, Pervasive has changed the package naming conventions to be more compatible with Borland standards. Also, the runtime packages have been separated from the design time packages in order to comply with Borland requirements.

Future releases of PDAC components will follow these conventions. However, previous versions such as Delphi 5 will retain the previous file naming scheme.

Updated Package Names Starting with Delphi 6

The following shows how to interpret the new runtime package names if you are coming from a previous version of Delphi and PDAC: 

pc200r60.bpl 
pb200r60.bpl 
ps200r60.bpl 
 





  
  
     

Filename digit position



     

Possible values



     

Meaning





  
     

1



     

p



     

Pervasive





  
     

2



     

c, b, or s



     

Common, Btrieve, or SQL





  
     

3-5



     

depends on release



     

Major and minor version of PDAC components





  
     

6



     

r, d



     

Runtime or Designtime





  
     

7-8



     

depends on release



     

Version of Delphi to which these components apply












 




 Note


Starting with Delphi 6, InfoPower functionality has been merged into the main packages. There are no longer separate packages for InfoPower Woll2Woll components.
Installing PDAC for Delphi 6

In the Delphi IDE, set the appropriate options as follows:

  1. From the Menu, select Project | Options
  2. Click the "Packages" tab.

    3. To have the application dynamically link with the PDAC libraries at runtime, make sure "Build with runtime packages" is checked, and add the appropriate PDAC packages to the edit box's list, as follows:

    [If the PDAC packages were added to the Build list at installation, this step is not necessary.]

    If the application uses the components on the left column of the following table, the packages (.DCP FILES) from the right column must appear in the build list.

    Components Used
    Packages Required
    [Transactional]
    TPvSession,
    TPvDatabase,
    TPvTable,
    TPvBatchMove,
    TwwPvTable
    pc200r60, pb200r60
    [Relational]
    TPvSQLSession,
    TPvSQLDatabase,
    TPvQuery,
    TPvUpdateSQL,
    TPvSQLStoredProc,
    TwwPvQuery,
    TwwPvSQLStoredProc
    pc200r60, ps200r60

To select packages, click Add, then Browse, and select the packages from the \PVSW\SDK\PDAC\Delphi6\LIB directory (for a default installation). All the packages may be selected at once.

Note
If the PDAC packages are not added to the list, they will be compiled into the executable and the shared libraries will not be used, even if the box is checked.

To statically link the PDAC libraries into the application's executable, make sure "Build with runtime packages" is unchecked.

If "Build with runtime packages" is checked at compile time, the following libraries must be installed when the application is deployed, in addition to the application itself, drm.dll, and any other packages or DLLs it requires:

From \PVSW\SDK\PDAC\Delphi6\REDIST, if their respective .DCP files are in the package build list: 

pc200r60.bpl 
pb200r60.bpl 
ps200r60.bpl

These files may be installed in the same subdirectory as the application's executable, but Pervasive recommends placing them in the target machine's path so they may be shared by other applications. \PVSW\bin is a good choice, on computers where it is the primary Pervasive executable directory.

In addition, the Delphi - PDAC application will require an installation of either a Pervasive.SQL engine (Server or Workgroup) or a Pervasive.SQL client and a remote server appropriately installed and configured.

Building and Deployment Instructions for Delphi 7

In the Delphi IDE, set the appropriate options as follows:

  1. From the Menu, select Project | Options
  2. Click the "Packages" tab.

    3. To have the application dynamically link with the PDAC libraries at runtime, make sure "Build with runtime packages" is checked, and add the appropriate PDAC packages to the edit box's list, as follows:

    [If the PDAC packages were added to the Build list at installation, this step is not necessary.]

    If the application uses the components on the left column of the following table, the packages (.DCP FILES) from the right column must appear in the build list.

    Components Used
    Packages Required
    [Transactional]
    TPvSession,
    TPvDatabase,
    TPvTable,
    TPvBatchMove,
    TwwPvTable
    pc200r70, pb200r70
    [Relational]
    TPvSQLSession,
    TPvSQLDatabase,
    TPvQuery,
    TPvUpdateSQL,
    TPvSQLStoredProc,
    TwwPvQuery,
    TwwPvSQLStoredProc
    pc200r70, ps200r70

To select packages, click Add, then Browse, and select the packages from the \PVSW\SDK\PDAC\Delphi7\LIB directory (for a default installation). All the packages may be selected at once.

Note
If the PDAC packages are not added to the list, they will be compiled into the executable and the shared libraries will not be used, even if the box is checked.

To statically link the PDAC libraries into the application's executable, make sure "Build with runtime packages" is unchecked.

If "Build with runtime packages" is checked at compile time, the following libraries must be installed when the application is deployed, in addition to the application itself, drm.dll, and any other packages or DLLs it requires:

From \PVSW\SDK\PDAC\Delphi7\REDIST, if their respective .DCP files are in the package build list: 

pc200r70.bpl 
pb200r70.bpl 
ps200r70.bpl

These files may be installed in the same subdirectory as the application's executable, but Pervasive recommends placing them in the target machine's path so they may be shared by other applications. \PVSW\bin is a good choice, on computers where it is the primary Pervasive executable directory.

In addition, the Delphi - PDAC application will require an installation of either a Pervasive.SQL engine (Server or Workgroup) or a Pervasive.SQL client and a remote server appropriately installed and configured.

Chapter contents
Publication contents

Prev topic: Differences Between Pervasive and Borland Implementation
Next topic: PDAC Security