SDAC requires OLE DB to be installed on the workstation. In current versions of Microsoft Windows, as Windows 2000, OLE DB is already included as standard package. But it is highly recommended to download the latest version (newer than 2.5) of Microsoft Data Access Components (MDAC).
Many features of SQL Server like Query Notifications, MARS require Microsoft SQL Server Native Client. If you need to use these features, you should download and install Microsoft SQL Server Native Client.
For applications that use SQL Server Compact Edition, the server itself is required to be installed on the client computer.
In order to use extended abilities of UDT fields , you will need to deploy the Devart.Sdac.UDTProxy.dll file with your application. This file should be present in the directory with your application, or registered in GAC.
SDAC 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.
You can check that 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.
If you are evaluating deploying Windows applications with SDAC Trial Edition, you will need to deploy the following BPL files:
and their dependencies (required IDE BPL files) with your application, even if it is built without 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:
|dacvclXX.bpl||if your application uses the SdacVcl unit|
|sdacvclXX.bpl||if your application uses the SdacVcl unit|
|crcontrolsXX.bpl||if your application uses the CRDBGrid component|