DataBind Controls to Sage 300 Data in C++Builder

Ready to get started?

Download for a free trial:

Download Now

Learn more:

Sage 300 ODBC Driver

The Sage 300 ODBC Driver is a powerful tool that allows you to connect with live data from Sage 300, directly from any applications that support ODBC connectivity.

Access Sage 300 data like you would a database - read, write, and update Sage 300 Invoices, Receipts, Refunds, etc. through a standard ODBC Driver interface.



DataBind to Sage 300 data in C++Builder with standard components and controls.

The CData ODBC Driver for Sage 300 makes it easy to integrate connectivity to live Sage 300 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 Sage 300 data, executes queries, and displays the results in a grid. An additional section shows how to use FireDAC components to execute commands from code.

Create a FireDAC Connection to Sage 300 Data

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.

Sage 300 requires some initial setup in order to communicate over the Sage 300 Web API.

  • Set up the security groups for the Sage 300 user. Give the Sage 300 user access to the option under Security Groups (per each module required).
  • Edit both web.config files in the /Online/Web and /Online/WebApi folders; change the key AllowWebApiAccessForAdmin to true. Restart the webAPI app-pool for the settings to take.
  • Once the user access is configured, click https://server/Sage300WebApi/ to ensure access to the web API.

Authenticate to Sage 300 using Basic authentication.

Connect Using Basic Authentication

You must provide values for the following properties to successfully authenticate to Sage 300. Note that the provider reuses the session opened by Sage 300 using cookies. This means that your credentials are used only on the first request to open the session. After that, cookies returned from Sage 300 are used for authentication.

  • Url: Set this to the url of the server hosting Sage 300. Construct a URL for the Sage 300 Web API as follows: {protocol}://{host-application-path}/v{version}/{tenant}/ For example, http://localhost/Sage300WebApi/v1.0/-/.
  • User: Set this to the username of your account.
  • Password: Set this to the password of your account.

You can then follow the steps below to use the Data Explorer to create a FireDAC connection to Sage 300.

  1. In a new VCL Forms application, expand the FireDAC node in the Data Explorer.
  2. Right-click the ODBC Data Source node in the Data Explorer.
  3. Click Add New Connection.
  4. Enter a name for the connection.
  5. In the FireDAC Connection Editor that appears, set the DataSource property to the name of the ODBC DSN for Sage 300.

Create VCL Applications with Connectivity to Sage 300 Data

Follow the procedure below to start querying Sage 300 data from a simple VCL application that displays the results of a query in a grid.

  1. Drop a TFDConnection component onto the form and set the following properties:

    • ConnectionDefName: Select the FireDAC connection to Sage 300.
    • Connected: Select True from the menu and, in the dialog that appears, enter your credentials.
  2. Drop a TFDQuery component onto the form and set the properties below:

    • Connection: Set this property to the TFDConnection component, if this component is not already specified.
    • SQL: Click the button in the SQL property and enter a query. For example:

      SELECT InvoiceUniquifier, ApprovedLimit FROM OEInvoices WHERE AllowPartialShipments = 'Yes'
    • Active: Set this property to true.
  3. Drop a TDataSource component onto the form and set the following property:

    • DataSet: In the menu for this property, select the name of the TFDQuery component.
  4. Drop a TDBGrid control onto the form and set the following property:

    • DataSource: Select the name of the TDataSource.
  5. Drop a TFDGUIxWaitCursor onto the form — this is required to avoid a run-time error.

Execute Commands to Sage 300 with FireDAC Components

You can use the TFDConnection and TFQuery components to execute queries to Sage 300 data. This section provides Sage 300-specific examples of executing queries with the TFQuery component.

Connect to Sage 300 Data

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 Sage 300 ODBC Source"; FDConnection1->Connected = true;

To connect the TFDQuery component to Sage 300 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.

Create Parameterized Queries

To create a parameterized query, use the following syntax below:

FDQuery1->SQL->Text = "select * from OEInvoices where allowpartialshipments = :AllowPartialShipments"; FDQuery1->ParamByName("allowpartialshipments")->AsString = "Yes"; query->Open();

The example above binds a string-type input parameter by name and then opens the dataset that results.

Prepare the Statement

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.

Execute a Query

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 OEInvoices where allowpartialshipments = :AllowPartialShipments"; FDQuery1.ParamByName("allowpartialshipments")->AsString = "Yes"; FDQuery1->Open();