Standard FireDAC Access to Microsoft Project
The MS Project FireDAC Components offers the most natural way to access Microsoft Project data from any
Delphi or C++ Builder application. Simply use MS Project FireDAC Components objects to connect and access data just as you
would access any traditional database. You will be able to use the MS Project FireDAC Components through
RAD Studio, in code through familiar classes, and in data controls like TDBGrid, TDBCtrlGrid, etc.
The CData FireDAC Components for MS Project hides the complexity of accessing data and provides additional powerful security features,
smart caching, batching, socket management, and more.
Working with the FireDAC Components, etc.
The MS Project FireDAC Components has the same architecture as the native Delphi & C++ Builder FireDAC Components for SQL Server
and can be accessed the same way.
For example:
FDConnection1.Name := 'Microsoft ProjectConnection';
FDConnection1.DriverName := 'CData.Fire.Microsoft Project';
with FDConnection1.Params as
TFDPhysCDataMicrosoft ProjectConnectionDefParams do begin
...
end;
FDConnection1.Connected := true;
FDQuery1.Active := true;
FDQuery1.Open('select * from Projects where id = ''...''');
...
More Than Read-Only: Full Update/CRUD Support
MS Project FireDAC Components goes beyond read-only functionality to deliver full
support for Create, Read, Update, and Delete operations (CRUD). Your end-users can interact
with the data presented by the MS Project FireDAC Components as easily as interacting with
a database table.
FireDAC Components Performance
With traditional approaches to remote access, performance bottlenecks can spell disaster
for applications. Regardless if an application is created for internal use, a commercial project, web, or mobile
application, slow performance can rapidly lead to project failure. Accessing data from any remote source has the potential
to create these problems. Common issues include:
- Network Connections - Slow network connections and latency issues are common in mobile applications.
- Service Delays - Delays due to service interruptions, resulting in server hardware or software updates.
- Large Data - Intentional or unintentional requests for large amounts of data.
- Disconnects - Complete loss of network connectivity.
The CData FireDAC Components for MS Project solves these issues by supporting powerful smart caching technology that can greatly
improve the performance and dramatically reduce application bottlenecks.
Smart Caching
Smart caching is a configurable option that works by storing queried data into a local database. Enabling smart
caching creates a persistent local cache database that contains a replica of data retrieved from the remote source.
The cache database is small, lightweight, blazing-fast, and it can be shared by multiple
connections as persistent storage.
Caching with our FireDAC Componentss is highly configurable, including options for:
-
Auto Cache - Maintain an automatic local cache of data on all requests. The provider will automatically
load data into the cache database each time you execute a SELECT query. Each row returned by the query will
be inserted or updated as necessary into the corresponding table in the cache database.
-
Explicit Cache - Cache only on demand. Developers decide exactly what data gets stored in the cache
and when it is updated. Explicit caching provides full control over the cache contents by using explicit
execution of CACHE statements.
- No Cache - All requests access only live data and no local cache file is created.
This powerful caching functionality increases application performance and allows applications to disconnect
and continue limited functioning without writing code for additional local storage and/or
data serialization/deserialization.
More information about FireDAC Components caching and best caching practices is available in the included
help files.
