The CData ODBC Driver for Office 365 makes it easy to integrate connectivity to live Office 365 data with standard data access components in C++Builder. This article shows how to create a simple visual component library (VCL) application in C++Builder that connects to Office 365 data, executes queries, and displays the results in a grid. An additional section shows how to use FireDAC components to execute commands from code.
Follow the steps below to use the Data Explorer to create a FireDAC connection to Office 365.
Below is a typical connection string:
OAuthClientId=MyApplicationId;OAuthClientSecret=MyAppKey;OAuthCallbackURL=http://localhost:33333;
See the "Getting Started" chapter in the help documentation for a guide to setting the required properties in the Microsoft ODBC Data Source Administrator.
Follow the procedure below to start querying Office 365 data from a simple VCL application that displays the results of a query in a grid.
Drop a TFDConnection component onto the form and set the following properties:
Drop a TFDQuery component onto the form and set the properties below:
SQL: Click the button in the SQL property and enter a query. For example:
SELECT * FROM Files
Drop a TDataSource component onto the form and set the following property:
Drop a TDBGrid control onto the form and set the following property:
You can use the TFDConnection and TFQuery components to execute queries to Office 365 data. This section provides Office 365-specific examples of executing queries with the TFQuery component.
To connect to the data source, set the Connected property of the TFDConnection component to true. You can set the same properties from code:
FDConnection1->ConnectionDefName = "CData Office 365 ODBC Source";
FDConnection1->Connected = true;
To connect the TFDQuery component to Office 365 data, set the Connection property of the component. When a TFDQuery component is added at design time, its Connection property is automatically set to point to a TFDConnection on the form, as in the application above.
To create a parameterized query, use the following syntax below:
FDQuery1->SQL->Text = "select * from Files where userid = :UserId";
FDQuery1->ParamByName("userid")->AsString = "54f34750-0d34-47c9-9949-9fac4791cddb";
query->Open();
The example above binds a string-type input parameter by name and then opens the dataset that results.
Preparing statements is costly in system resources and time. The connection must be active and open while a statement is prepared. By default, FireDAC prepares the query to avoid recompiling the same query over and over. To disable statement preparation, set ResourceOptions.DirectExecute to True; for example, when you need to execute a query only once.
To execute a query that returns a result set, such as a select query, use the Open method. The Open method executes the query, returns the result set, and opens it. The Open method will return an error if the query does not produce a result set.
FDQuery1->SQL->Text := "select * from Files where userid = :UserId";
FDQuery1.ParamByName("userid")->AsString = "54f34750-0d34-47c9-9949-9fac4791cddb";
FDQuery1->Open();
To execute a query that does not return a result set, use the ExecSQL method. The ExecSQL method will return an error if the query returns a result set. To retrieve the count of affected rows for an insert, update, or delete, use the TFD.RowsAffected property.
FDQ.SQL.Text := "delete from Files where Id = :Id";
FDQuery1->Params->Items[0]->AsString = "x12345";
FDQuery1->ExecSQL();
AnsiString i = FDQuery1->RowsAffected;