A familiar interface.
A T24-aware connection.

01 / CONNECTIONS

Choose the path for your environment.

T24Dac exposes T24 data through ODBC and JDBC. Your application connects to the T24Dac server, which uses a configured backend connection to retrieve records.

Client drivers

• ODBC: Windows drivers in 32-bit and 64-bit versions. Match the driver architecture to the calling application.
• JDBC: a Java type 3 driver for Java applications and compatible SQL or ETL clients.
• Server: a Windows service or console application that manages queries and result delivery.

02 / DATA FLOW

What happens when you run a query?

1. Submit SQL. An ODBC or JDBC application sends a query to the T24Dac server.
2. Retrieve records. The configured provider selects the underlying T24 records from the backend.
3. Interpret T24 fields. Processing resolves fields and expands multivalues or subvalues according to the query and connection settings.
4. Prepare the result. The server writes normalized rows to a SQLite result database.
5. Return rows to the application. The client uses a local result file or downloads a remote result, then exposes the SQL result set.

Parallel selection and processing support extraction workloads. Actual performance depends on the backend, query, record shape, worker configuration and network.

Optional result packing reduces file-transfer size. In Oracle configurations, optional server-side data compression is a separate feature and requires the corresponding Oracle helper setup.

03 / SQL EXAMPLE

Start with a familiar query.

Select three account records, restrict the currency and order the result:

SELECT TOP 3 _ID, CUSTOMER, CATEGORY, CURRENCY
FROM F.ACCOUNT
WHERE CURRENCY = 'EUR'
ORDER BY _ID

Example: select the first three EUR accounts, ordered by record identifier.

F.ACCOUNT is the account table in this example. Use the table names and fields available in your own T24 environment.

Supported query patterns include column selection, filters, sorting, nested queries and grouped aggregates. The developer guide demonstrates aggregate operations over nested selections.

The homepage shows invented records to illustrate the result shape. It does not connect to a banking system.

04 / T24 FIELDS

Work with the structure behind the data.

Multivalues and subvalues

T24 records can contain repeated values. T24Dac supports expansion into result rows and selection of individual values or subvalues. Choose the behavior that matches the relationships in your record and the output your report needs.

Local fields and types

Local fields can be selected alongside standard fields. T24Dac recognizes some T24 data types automatically and supports explicit type conversion where needed.

TAFC-specific extensions

The documented TAFC extensions include linked fields, user-defined functions, stored procedures, concat/index helpers and jBASE EVAL. These features are specific to the TAFC path; do not assume equivalent behavior through a direct Oracle or MSSQL connector.

05 / PLAN YOUR SETUP

Bring the details that matter.

To discuss a suitable connection and evaluation, have these details ready:

• Your T24 release and runtime: TAFC or TAFJ.
• Your database backend and version.
• Your reporting, ETL or application client, and whether it uses ODBC or JDBC.
• The tables, field types and multivalue structures you need to query.
• The expected data volumes and reporting or extraction schedule.