![]() |
VOOZH | about |
The CData ODBC driver for XML makes it easy to integrate connectivity to live XML 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 XML data, executes queries, and displays the results in a grid. An additional section shows how to use FireDAC components to execute commands from code.
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
CData Drivers let you work with XML files stored locally and stored in cloud storage services like Box, Amazon S3, Google Drive, or SharePoint, right where they are.
Set the URI property to local folder path.
To connect to XML file(s) within Amazon S3, set the URI property to the URI of the Bucket and Folder where the intended XML files exist. In addition, at least set these properties:
To connect to XML file(s) within Box, set the URI property to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect to Box.
To connect to XML file(s) within Dropbox, set the URI proprerty to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect to Dropbox. Either User Account or Service Account can be used to authenticate.
To connect to XML file(s) within SharePoint with SOAP Schema, set the URI proprerty to the URI of the document library that includes the intended XML file. Set User, Password, and StorageBaseURL.
To connect to XML file(s) within SharePoint with REST Schema, set the URI proprerty to the URI of the document library that includes the intended XML file. StorageBaseURL is optional. If not set, the driver will use the root drive. OAuth is used to authenticate.
To connect to XML file(s) within Google Drive, set the URI property to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect and set InitiateOAuth to GETANDREFRESH.
The property is the controlling property over how your data is represented into tables and toggles the following basic configurations.
See the Modeling XML Data chapter for more information on configuring the relational representation. You will also find the sample data used in the following examples. The data includes entries for people, the cars they own, and various maintenance services performed on those cars.
You can then follow the steps below to use the Data Explorer to create a FireDAC connection to XML.
Follow the procedure below to start querying XML 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 [people].[personal.age] AS age, [people].[personal.gender] AS gender, [people].[personal.name.first] AS first_name, [people].[personal.name.last] AS last_name, [vehicles].[model], FROM [people] JOIN [vehicles] ON [people].[_id] = [vehicles].[people_id]
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 XML data. This section provides XML-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 XML ODBC Source"; FDConnection1->Connected = true;
To connect the TFDQuery component to XML 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 people where [ personal.name.last ] = :[ personal.name.last ]";
FDQuery1->ParamByName("[ personal.name.last ]")->AsString = "Roberts";
FDQuery1->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 people where [ personal.name.last ] = :[ personal.name.last ]";
FDQuery1->ParamByName("[ personal.name.last ]")->AsString = "Roberts";
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 use the TFD.RowsAffected property.
FDQuery1->SQL->Text = "delete from people where Id = :Id";
FDQuery1->Params->Items[0]->AsString = "x12345";
FDQuery1->ExecSQL();
AnsiString i = FDQuery1->RowsAffected;
ShowMessage("Rows affected: " + i);
Below you can find other articles for using the CData ODBC Driver with RAD Studio, Delphi, and C++ Builder.
Download a free trial of the XML ODBC Driver to get started:
Download NowLearn more:
👁 XML Documents IconThe XML ODBC Driver is a powerful tool that allows you to connect with live XML data stores, directly from any applications that support ODBC connectivity.
Access XML data like you would any standard database - read, write, and update etc. through a standard ODBC Driver interface.