UniDAC

Deployment

UniDAC applications can be  built and deployed with or without run-time libraries. Using run-time libraries is managed with the "Build with runtime packages" check box in the Project Options dialog box.

Deploying Windows applications built without run-time packages

You do not need to deploy any files with UniDAC-based applications built without run-time packages, provided you are using a registered version of UniDAC.

You can check your application does not require run-time packages by making sure the "Build with runtime packages" check box is not selected in the Project Options dialog box.

Trial Limitation Warning

If you are evaluating deploying Windows applications with UniDAC Trial Edition, you will need to deploy the following DAC BPL files:

dacXX.bpl always
unidacXX.bpl always

and their dependencies (required IDE BPL files) with your application, even if it is built without run-time packages:

rtlXX.bpl always
dbrtlXX.bpl always
vcldbXXX.bpl always

Deploying Windows applications built with run-time packages

You can set your application to be built with run-time packages by selecting the "Build with runtime packages" check box in the Project Options dialog box before compiling your application.

In this case, you will also need to deploy the following BPL files with your Windows application:

dacXX.bpl always (XX means the Delphi version: XX equals to 70 for Delphi 7, XX equals to 105 for Delphi 2007, etc.)
dacvclXX.bpl if your application uses the UniDacVcl unit
unidacXX.bpl always
unidacvclXX.bpl if your application uses the UniDacVcl unit
XXXproviderXX.bpl for each used provider (e.g.: OraProvider70.bpl is the file belonging to the Oracle provider for Delphi 7)
XdacXX.bpl* for each used provider with UniDAC Express Edition, never used with UniDAC Professional or Standard edition
crcontrolsXX.bpl if your application uses the CRDBGrid component

*It is not required to deploy XdacXX.bpl files with UniDAC Professional and Standard editions. But it is necessary to deploy XdacXX.bpl files with Express Edition of UniDAC. This happens because in UniDAC Professional and Standard editions functionality of XdacXX.bpl is included in the correspondent XXXproviderXX.bpl, when in Express Edition of UniDAC, XXXproviderXX.bpl is just a wrapper on XdacXX.bpl.

© 1997-2020 Devart. All Rights Reserved. Request Support DAC Forum Provide Feedback