The CData FireDAC Components for Sage 300 models Sage 300 objects as relational tables and views. A Sage 300 object has relationships to other objects; in the tables, these relationships are expressed through foreign keys.
- The component models Sage 300 entities as relational tables and views, allowing you to write SQL to query Sage 300 data.
- Stored procedures allow you to execute operations to Sage 300.
- Live connectivity to these objects means any changes to your Sage 300 account are immediately reflected when using the component.
Tables are retrieved dynamically from the authenticated Sage 300 account.
Child TablesChild tables are also retrieved, which contain child objects of their parents. For example, OEOrders has OEOrders_OrderCommentsInstructions and OEOrders_OrderDetails as its child tables. These tables are exposed as aggregate columns while querying their parent table. They also have references to the unique identifier of their parent.
Read-only views are retrieved dynamically from the authenticated Sage 300 account.
Stored Procedures are function-like interfaces to Sage 300. Stored procedures allow you to execute operations to Sage 300.
Collaborative Query Processing
The component offloads as much of the SELECT statement processing as possible to Sage 300 and then processes the rest of the query in memory. API limitations and requirements are also documented in this section.
See SupportEnhancedSQL for more information on how the component circumvents API limitations with in-memory client-side processing.
SELECT statements for the main tables are mostly supported server-side. For example:
SELECT * FROM APInvoiceBatches WHERE BatchDate='2019-01-09 01:00:00.0'will be run server-side.
Note: When executing SELECT statements on child tables, everything is processed client side.