apollo 7.3 d7-xe3

Overview The Apollo Embedded VCL components are native data-aware Delphi components for building Win32 applications using Delphi and C++Builder. Key Features ◦Create Win32 applications using Delphi and C++Builder (Borland, Embarcadero, CodeGear) ◦Create, update and manage CA-Clipper and FoxPro DBF/Xbase database files from code ◦BDE not required ◦Over 30x smaller than the BDE (500KB vs 20MB) ◦Includes Delphi VCL source code to components ◦Compatible with VCL data aware components including TDataset and 3rd party components ◦Samples with full source code ◦Easily scalable from embedded to client/server configuration with little code changes ◦Royalty free unlimited distribution Supported Embarcadero, Borland CodeGear IDEs ◦RAD Studio XE6, XE5, XE4, XE3, XE2, XE, 2010, 2009, 2007 ◦Delphi XE6, XE5, XE4, XE3, XE2, XE, 2010, 2009, 2007, 2006, 2005, 7, 6, 5 ◦C++Builder XE6, XE5, XE4, XE3, XE2, XE, 2010, 2009, 2007, 2006, 5 Supported Languages ◦Delphi/Object Pascal ◦C++Builder/C++Supported Platforms ◦Win32 Borland BDE Replacement The BDE is an awkward collection of database technologies that performs various unrelated functions including third party database connectivity and native database management of legacy dBASE and Paradox database files. This collection of unrelated functionality adds needless overhead to your applications and is the source of many configuration, deployment and BDE versioning issues -- all of which can be avoided by replacing the BDE with Apollo. Among other reasons to avoid developing applications that use the BDE is the fact that Borland has deprecated the BDE and has not issued updates to the BDE since 1999. In summary, there is no future in using the BDE. TDataset Compatible Apollo VCL components are fully compatible with Borland's TDataset architecture, which means Apollo is fully compatible with all data aware components including TDBGrid, TDBEdit etc. Apollo is also compatible