Autonomous REST Connector ODBC 8.0.1 Windows
- Last Updated: May 8, 2026
- 20 minute read
- OpenAccess SDK
- Documentation
README
Progress(R) DataDirect(R)
Progress(R) DataDirect(R) Autonomous REST Connector(R) for ODBC
Windows Platforms(32- and 64-bit)
8.0.1 Release
February 2026
***********************************************************************
Copyright (C) 2026 Progress Software Corporation and/or its
subsidiaries or affiliates. All Rights Reserved.
***********************************************************************
CONTENTS
Post-GA Product Announcements
Installation Directory
Requirements
Data Source and Platform Support
Changes Since 8.0.1 GA
Changes for 8.0.1 GA
Release 8.0.0 Features
Notes, Known Problems, and Restrictions
Driver Workaround Options
Documentation
Installed Files for 32-bit Drivers
Installed Files for 64-bit Drivers
Post-GA Product Announcements
The readme files will no longer be updated with product announcements and new
features after the General Availability (GA) of the product. For the latest
updates and enhancements, please refer to the release notes
(https://www.progress.com/datadirect-connectors/whats-new).
Installation Directory
* The default installation directory for the 32-bit driver on a 64-bit
system is:
C:\Program Files (x86)\Progress\DataDirect\ODBC
* The default installation directory for all other installations is:
C:\Program Files\Progress\DataDirect\ODBC
Requirements
* The installer program requires a JVM that is Java SE 11 or higher, including
Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
* The driver requires a Java Virtual Machine (JVM): Java SE 8 or higher,
including Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
* The driver requires the following runtime library:
Microsoft Visual C/C++ runtime version 14.40.33810 or higher
* IMPORTANT: You must have the Microsoft Data Access Components (MDAC)
installed to use this product.
- For 32-bit Windows systems, version 2.6 or higher is required.
- For 64-bit Windows systems, version 2.8 or higher is required.
Depending on the version of your Windows operating system, these
components may already be installed. You can download a utility that
determines whether MDAC is installed and its version from the following
Microsoft site:
http://msdn.microsoft.com/en-us/data/aa937730.aspx
You can also download MDAC from the same site.
Data Source and Platform Support
For the latest data source and platform support information, refer to the
Product Compatibility Guide:
https://docs.progress.com/bundle/datadirect-product-compatibility/resource/
datadirect-product-compatibility.pdf
Changes Since 8.0.1 GA
CVE-2022-41853 - Use of Externally-Controlled Input to Select Classes or Code
('Unsafe Reflection')
-----------------------------------------------------------------------------
Several Progress DataDirect ODBC drivers utilized a version of HyperSQL
Database that was vulnerable to remote code execution described in
CVE-2022-41853. All impacted drivers have been patched to fix this
vulnerability. For details on impacted drivers and fixed versions, refer to
the following KB article:
https://community.progress.com/s/article/DataDirect-ODBC-Critical-Security-
Bulletin-November-2022-CVE-2022-41853
Enhancements
------------
* The product package now includes .pdb files. These files contain
debugging symbols that can be used for diagnosing and debugging issues
in the driver.
* The Qualify Normalized Names option has been added to the driver. This option
allows you to configure whether the names of relational tables normalized
from array columns are derived directly from the column name or prefixed with
parent object names.
* The driver has been enhanced to support OAuth 2.0 flows that require client
credentials be specified in the body of a POST request. You can configure
the driver to send client credentials in the body of a POST request using
the new 0 (POST) setting for the OAuth Client Credentials Mode
(ClientCredentialsMode) option.
* The driver is now compiled with a Visual Studio 2022 compiler for Windows
platforms. As a result, you must have Microsoft Visual C/C++ runtime
version 14.40.33810 or higher on your machine to run the driver.
* The following enhancements have been made to improve how the driver handles
assigning primary keys for tables:
- The logic the driver uses to assign the default primary key has been
improved to provide more accurate results.
- A list of viable primary key candidates can be reviewed by querying the
INFORMATION_SCHEMA.SYSTEM_SAMPLING_STATUS system table. If you need to
designate a primary key other than the default, the PRIMARY_KEY_CANDIDATES
column provides you with a quick reference of candidates ranked by the how
well they satisfy the primary key criteria.
- The driver has been enhanced to generate a primary key column, ROWID, if no
viable candidates were discovered during sampling.
* The driver has been enhanced to detect JSON roots in endpoint responses
during sampling. When mapping the response, the driver maps the embedded
objects in the root to a dedicated table. You can modify the detected JSON
root for an endpoint using the JSON Root field in the Autonomous REST
Composer or the JSON Root (JSONRoot) option.
* The ICU library files that are installed with the product have been
upgraded to version 74.1. As a part of this upgrade, the ICU library
file names have changed:
- For the 32-bit driver: From ivicu28.dll to ivicu.dll
- For the 64-bit driver: From ddicu28.dll to ddicu.dll
This upgrade is available starting in build 08.02.1072 of the ICU
library files.
* The driver has been enhanced to successfully connect and expose a schema even
if some of the endpoints in the Model are unable to be sampled. To support
this new behavior, the following new features have been introduced:
- The driver now supports configurable failure tolerance when sampling
endpoints. By configuring the new Sampling Failure Tolerance
(SamplingFailureTolerance) option, you can specify the number of endpoints
for which sampling can fail before the driver fails the connection.
- The driver has been enhanced to allow you to review the status of endpoints
to verify that they have been successfully sampled. You can query the
statuses of your endpoints in the new
INFORMATION_SCHEMA.SYSTEM_SAMPLING_STATUS system table.
* The driver has been enhanced to support OAuth 2.0 flows that require client
credentials be specified in only a basic authentication header or only as a
URL parameter to request an access token. You can configure how client
credentials are sent in a request using the OAuth Client Credentials Mode
(ClientCredentialsMode) option.
* The driver has been enhanced to support specifying default filter values
(WHERE clauses) for SQL queries. You can specify your list of default
parameters using the Default Query Options (DefaultQueryOptions) options.
* The driver's next page token paging support has been enhanced to use URLs,
query parameter values, and HTTP header values that are returned in either a
response body and header. To configure these mechanisms, the driver has added
support for the new nextPageRequestHeader and nextPageResponseHeader
parameters in the Model files.
* The Configuration Manager has been enhanced to simplify configuring OAuth 2.0
authentication. When specifying one of the new grant flow specific values for
the Authentication Method (AuthenticationMethod) option, the Configuration
Manager exposes only options related to your grant flow. This functionality
assists you in configuring your grant flow by showing you what information
the driver needs to authenticate. Note that the existing OAuth2 value for
the Authentication Method option will continue to be supported.
* The driver has been enhanced to the support the JWT (JSON Web Token) bearer
grant for OAuth 2.0 authentication. You can configure the JWT bearer grant
authentication using the new Claims Issuer, Claims Subject, JWT Certificate
Alias, JWT Certificate Password, and JWT Certificate Store options.
* The driver has been enhanced to support the PKCE grant type for OAuth 2.0
authentication.
* The driver has been enhanced to support next token paging for APIs that use
a query parameter (for example, starting_after) to determine what data value
to start after, when returning the next page of results.
* The driver has been enhanced to support issuing POST requests with an empty
body. You can enable this functionality using the new #omitWhenEmpty
modifier in the REST model file.
* The driver has been enhanced to support fetching access and refresh tokens at
connection when OAuth 2.0 is enabled. When using the new dynamic
authorization code grant, you can initiate an authorization code grant flow
by specifying login credentials using the login prompt for your REST service,
thereby providing a method to authenticate without fetching access and
refresh tokens via the Configuration Manager or third-party application. In
addition, the new Enable Login Prompt (EnableLoginPrompt) option has been
added to configure this functionality.
* Update operation functionality has been enhanced to support APIs that require
using PATCH, PUT, or POST methods that send only changed fields in the body.
You can configure update operations using the #update and #sendonlyupdated
parameters in the Model file.
* The driver has been enhanced to support designating columns as read-only
using the model file with the new #readonly element. See for more
information.
* The driver has been enhanced to support flagging columns as nullable using
the model file with the new #notnull element. See for more information.
* The driver has been enhanced to support write operations, including Insert,
Update, and Delete statements. To enable write operations for an endpoint and
the relational tables derived from the endpoint, you must configure the new
#insert,#update, #delete parameters in the Model file.
* The driver has been updated with the new JSON Root (JSONRoot) connection
option, which allows you to limit the results mapped to tables to only the
specified object when you have multiple objects in an endpoint. This option
provides a method to map only the data relevant to your application.
* The Autonomous REST Composer has been enhanced to allow you to define
parameter values in endpoints as variables. This functionality simplifies
the sharing of Model files by allowing you to designate user-specific values
as variables. Users with whom you share the file can then provide values for
these variables that are replaced across their REST model file, allowing
them to quickly customize the endpoints according to their use cases.
* The Autonomous REST Composer has been enhanced to allow you to limit the
values displayed in the Authentication Method drop-down field to only those
supported by the data source, instead of all those supported by the driver.
You can select which fields you want to display by selecting them from the
Configure Authentication Method(s) field on the Connection tab.
Changed Behavior
----------------
* The behavior of the OAuth Client Credentials Mode (ClientCredentialsMode)
option has been updated:
- The behavior of the 0 setting has been changed so that client credentials
are sent only as a basic authentication header. For earlier builds of the
driver, client credentials were sent as both a basic authentication header
and a URL parameter.
- The 0 (All) setting has been changed to 0 (Default) in the Configuration
Manager and documentation to reflect the new behavior.
- The default setting for the OAuth Client Credentials Mode is 0 (Default).
* The installer program now requires you to install a JRE that is Java SE 11 or
higher before running the installer. In earlier versions, the JRE used by the
installer program was included in the product. However, to avoid potential
security vulnerabilities, the installer program no longer includes a JRE.
Instead, the installer program uses the JRE in your environment to allow for
the most secure version of a JRE to be used.
Notes:
- This change does not affect the JVM requirements for the driver. For the latest
driver requirements, refer to the Product Compatibility Guide:
https://docs.progress.com/bundle/datadirect-product-compatibility/resource/
datadirect-product-compatibility.pdf
- The installer program cannot remove the already installed JRE files from the
install directory automatically. Remove them manually.
- To install the 32-bit drivers on 64-bit Windows platforms and start the SQL
engine service, the installer requires the 32-bit version of Java SE 11 or
higher installed on your machine and defined on your path.
* Pendo.io is no longer installed with the product. As a result, the evaluation
version of the ODBC Configuration Manager no longer tracks user interactions
to identify potential issues and workflow improvements.
* The evaluation version of the driver has been enhanced with Pendo.io in order
to track user interaction with the ODBC Configuration Manager. Telemetry data
will be analyzed to identify user workflows and potential issues with the
interface. The collected data will then be used to define improvements that
will result in a better user experience. Note that Pendo.io only tracks
interactions with the product and does not capture user specific connection
property values or any personally identifiable information.
* The installer program has been updated to no longer install common components
for drivers that do not use them. As a result, the installer program no longer
installs the following common components for the Autonomous REST Connector:
- OpenSSL library files, such as ivopenssl30.dll, ddopenssl30.dll, fips.dll,
and openssl.cnf.
- Curl library files, such as ivcurl28.dll and ddcurl28.dll.
If the files are not used by any other DataDirect driver on your machine, you
can safely remove them from existing product directories.
Changes for 8.0.1 GA
Enhancements
------------
* The driver now includes the DataDirect ODBC Driver Configuration Manager for
quick configuration and testing of your driver. This Configuration Manager
allows you to:
- Configure data sources
- Generate and edit connection strings
- Test connect data sources and connection strings
- Execute SQL commands for testing
- Fetch OAuth tokens and configure OAuth
- Access connection option descriptions and the full product documentation
* The DataDirect ODBC Configuration Manger has been enhanced to support the
generation of Model files. This provides you with a method to quickly
generate and edit a Model file.
* The driver now includes a library of Progress developed prebuilt Model
files to connect to publicly accessible REST services. The Model files
define the requests and pagination settings for a data source, eliminating
the need to create your own Model file. After selecting your data source
from the Autonomous REST Composer, you only need to provide your authentication
credentials to begin accessing your data.
* The Configuration Manager has been enhanced with role-specific work flows:
- The developer view of the Configuration Manager, the Autonomous REST
Composer, provides access to the new Models library and configuration
options. In addition, the Hub window has been added that includes access
to training videos, documentation, and technical support. The developer's
view can be launched through the new desktop and Start menu icons.
- The user's view provides a simplified interface that allows you to
configure and test your connection. You can launch the user's view through
the ODBC Administrator.
* The driver now supports responses returned in XML and CSV formats in addition
to JSON. When sampling an endpoint, the driver detects the format of the
response before mapping the objects to the relational view of the data. If
multiple formats are supported by the service, the driver defaults to using
JSON; however, you can also configure the driver to use your preferred format.
* The driver has been enhanced to support issuing POST requests that use custom
parameters. This allows for filtering in scenarios where complex parameter
syntax is employed, such as using complicated JSON data or empty arrays.
* The driver has been enhanced to support passing custom HTTP headers when
using OAuth 2.0 authentication. When OAuth 2.0 is enabled
(AuthenticationMethod=OAuth2), you can now pass the HTTP header name with the
Authentication Header (AuthHeader) option and the ID value with the Security
Token (SecurityToken) option. This functionality can be used for passing the
ID string for tenant ID authentication.
* The driver has been enhanced to support AWS (Amazon Web Services) credentials
authentication. When AWS credentials authentication is enabled
(AuthenticationMethod=43), you can configure AWS credentials using the new
Access Key (AccessKey), Region (Region), and Secret Key (SecretKey) options.
* The driver has been enhanced to support bearer token and digest
authentication.
* The new Health Check URI (HealthURI) connection option provides a method to
test connectivity for authentication methods, such as Basic, Digest, URL
Parameter-based, or HTTP header-based, that do not perform an explicit
action upon connection.
* The driver has been enhanced with the new Array Normalization Threshold
(ArrayNormalizationThreshold) connection option. Array Normalization
Threshold allows you to specify the length of arrays (in elements) at which
the driver begins to normalize arrays to child tables when generating a
flattened view. This provides you with a method to control the size and
focus of your parent table when encountering large arrays or nested arrays.
* The driver has been enhanced with the new User Agent String (UserAgent)
connection option. User Agent String allows you to specify the value of the
User-Agent header to be used in HTTP requests. This provides a method to
override the default value of the User-Agent header when required by a
service.
* The driver has been enhanced to support connecting through a proxy server.
You can configure this feature using the new Proxy Host (ProxyHost), Proxy
Port (ProxyPort), Proxy User (ProxyUser), and Proxy Password (ProxyPassword)
connection options.
* The new Encryption Method (EncryptionMethod) connection option allows you
to determine when TLS/SSL data encryption is enabled.
* The new Port Number (PortNumber) connection option allows you to specify the
port number of the server listener the TCP port of the server that is
listening for REST API requests.
* The new Refresh Dirty Cache (RefreshDirtyCache) connection option allows you
to determine whether the driver refreshes a dirty cache on the next fetch
operation from the cache.
* The new Refresh Schema (RefreshSchema) connection option allows you to
determine whether the driver automatically refreshes the relational map of
when connecting.
* The new Authorization URI (AuthURI) connection option allows you to specify
the endpoint used for obtaining an authorization code from a third-party
authorization service for OAuth 2.0 implementations.
* The new Statement Call Limit (StmtCallLimit) and Statement Call Limit
Behavior (StmtCallLimitBehavior) connection options allow you to limit the
number of calls made to your web service.
* The new Web Service Fetch Size (WSFetchSize) allows you to specify the number
of rows of data the driver attempts to fetch for each ODBC call. This
provides you with a method to tune the driver for your ideal balance
throughput and response time.
* The new Web Service Pool Size (WSPoolSize) specifies the maximum number of
sessions the driver uses. This allows the driver to have multiple web service
requests active when multiple ODBC connections are open, thereby improving
throughput and performance.
* The new Web Service Retry Count (WSRetryCount) connection options specifies
the number of times the driver retries a timed-out Select request.
* The new Web Service Timeout (WSTimeout) connection option specifies the time,
in seconds, that the driver waits for a response to a web service request.
* The driver has been enhanced to support the following new paging parameters
in the Model file: fieldListParameter, hasMoreElement, pageSizeElement,
totalPagesElement, and totalRowsElement.
* The driver has been enhanced to allow you to define custom authentication
requests, including the new Custom Auth Params (CustomAuthParams) connection
option. If your service does not support one of the standard authentication
methods supported by the driver, you can modify the Model file to define
token-based authentication flows.
* The driver has been enhanced to allow you to customize how HTTP response
status codes are processed by the driver. By configuring the Model file,
you can define error responses for codes that are returned by the service,
including driver actions and error messages.
* The driver has been enhanced to support OAuth 2.0 authentication.
* The driver has been enhanced to support requests for endpoints that use
custom HTTP-headers.
Changed behavior
----------------
* The attribute for User connection option has changed from LogonID to User.
* The Create Map (CreateMap), Refresh Schema (RefreshSchema), and Schema Map
(SchemaMap) options are no longer supported. The driver now generates the
schema map for each session and stores it internal memory.
* The supported valid values for the Authentication Method
(AuthenticationMethod) option have changed from enum to numeric types. If you
using a connection string or odbc.ini file for an earlier version of the
driver, you will need to update the values specified for these options.
* The Application Using Threads (ApplicationUsingThreads) connection option is
no longer supported. The driver now works with single-threaded and
multi-threaded applications for all connections.
* The Result Memory Size (ResultMemorySize) connection option is no longer
supported. The size of an intermediate result set is now determined by a
percentage of the max Java heap size.
* The IANAAppCodePage (IANAAppCodePage) connection option is longer supported.
IANAAppCodePage specified Internet Assigned Numbers Authority (IANA) value
if your application was not Unicode enabled or if your database character set
was not Unicode.
* The Login Timeout (LoginTimeout) is no longer supported. As a result,
connection requests do not timeout, but the driver responds to the
SQL_ATTR_LOGIN_TIMEOUT attribute.
* The Report Codepage Conversion Errors (ReportCodepageConversionErrors) is no
longer supported. As a result, the driver behavior has changed to substitute
0x1A for each character that cannot be converted and does not return a
warning or error.
Release 8.0.0 Features
The driver supports SQL read-only access to REST API data sources that
express payloads using the JSON format. To support SQL access to REST API data
sources, the driver creates a relational map of the JSON data model and
translates SQL statements provided by the application to native queries and Web
service calls. In addition, the driver supports multiple simultaneous sessions.
Features:
* The driver supports SQL read-only access to REST API endpoints that return
JSON payloads.
* The driver supports all ODBC Core and Level 1 functions and some Level 1 and
Level 2 features.
* The driver supports standard JSON data types and additional data types
through data type inference.
* The driver supports using internal memory or a configurable REST file to
define REST responses and relational mapping.
* The driver heuristically maps data types, eliminating the need to define
native data types in most scenarios.
* The driver supports basic, HTTP-header based, URL-Parameter based and no
authentication.
* The driver supports the handling of large result sets with configurable
paging and the Fetch Size and WSFetch Size connection options.
Notes, Known Problems, and Restrictions
The following are notes, known problems, and restrictions for the
8.0 release of the driver:
Specifying values for the same connection option multiple times
---------------------------------------------------------------
The driver does not support specifying values for the same connection
option multiple times in a connection string or DSN. If a value is
specified using the same attribute multiple times or using both
long and short attributes, the connection may fail or the driver may
not behave as intended.
Parsing Object Names with Spaces
--------------------------------
Currently, when parsing root-level JSON objects to map to table names during
the sampling process, the driver does not properly handle spaces in the name.
When the JSON root object name contains spaces, the driver uses only the
portion of the name before the first space to name the corresponding object in
the relational map. For example, if you sampled an object named "example
table", the driver would generate a corresponding table named "EXAMPLE",
instead of "EXAMPLE TABLE".
Out-of-memory Errors
--------------------
The driver has been designed to handle large result sets; however,
out-of-memory errors can still occur. The following items outline how to reduce
the likelihood of out-of-memory errors for your environment.
* Reduce FetchSize to reduce demands on memory. By lowering the maximum number
of rows as specified by FetchSize, you lower the number of rows the driver is
attempts to process before returning data to the application. Thus, you
reduce demands on memory and decrease the likelihood of out-of-memory errors.
* Decrease ResultMemorySize until results are successfully returned. Intermediate
results larger than the value specified will be written to disk as opposed to
held in memory. When configured correctly, this avoids memory limitations by
not relying on memory to process larger intermediate results. Be aware that
while writing to disk reduces the risk of out-of-memory errors, it also
negatively impacts performance. For optimal performance, decrease this value
only to a size necessary to avoid errors. By default, ResultMemorySize is set
to -1, which sets the maximum size of intermediate results held in memory to
a percentage of the max Java heap size. If you received errors using the
default configuration, use the max Java heap size divided by 4 as a starting
point when tuning this option.
* Increase the JVM heap size. By increasing the max Java heap size, you increase
the amount of data the driver can accumulate in memory and avoid
out-of-memory errors.
126 Error When Modifying Data Sources on Windows 10
---------------------------------------------------
You may receive a 126 error when adding or configuring a data source stored
on a network location. This might be caused by the settings of the User Account
Control (UAC) security feature on Windows 10. To work around this issue:
Important: Implementing this fix disables security safeguards that are designed
to protect your machine. Before starting, refer to the following Microsoft
documentation for potential risks associated with disabling the UAC feature:
http://windows.microsoft.com/en-us/
windows/what-are-user-account-control-settings
1. From the Start menu, type regedit in the search field; then, select regedit
from the results list. The Registry Editor window opens.
2. Navigate to the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. Right click on the subkey; then, select New > DWORD Value.
4. Rename the new value EnableLinkedConnections.
5. Right-click EnableLinkedConnections, and then click Modify. The Edit DWORD
Value window opens.
6. In the Value data field, type 1. Click OK.
7. Close the Registry Editor; then, restart your computer.
Driver WorkAround Options
Progress DataDirect has included non-standard connection options (workarounds)
for the driver that enable you to take full advantage of packaged ODBC-enabled
applications requiring non-standard or extended behavior. Refer to the chapter
"WorkAround options" in THE PROGRESS DATADIRECT FOR ODBC DRIVERS REFERENCE for a
description of these options.
Documentation
PROGRESS DATADIRECT AUTONOMOUS REST CONNECTOR FOR ODBC DOCUMENTATION SET
------------------------------------------------------------------------
The driver documentation set is available from the Progress Information Hub:
https://docs.progress.com/category/datadirect-autonomous-rest-connector
You can access the online help system directly in either of the following ways.
* Via the HTML redirect in the installation Help directory
* By selecting Help from the information menu (? button) in the Configuration
Manager
Installed Files for the 32-bit Driver
This file list assumes a full installation of the driver and
documentation.
The installer copies the following file to the Windows system
directory:
ivtrc28.dll DataDirect trace library
The installer copies the following files and subdirectories to the
product installation directory, by default:
For 32-bit drivers on 64-bit machines:
C:\Program Files (x86)\Progress\DataDirect\ODBC\:
For all other installations:
C:\Program Files\Progress\DataDirect\ODBC\:
\<install_dir>\:
----------------
license.txt Progress DataDirect license agreement
\drivers:
---------
ivautorest28.dll DataDirect Autonomous REST Connector
ivautorest28.pdb Debugging symbols for DataDirect Autonomous
REST Connector
ivautorest28r.dll DataDirect Autonomous REST Connector
resource file
ivicu.dll Unicode conversion tables
ivicu.pdb Debugging symbols for ICU library
IVODBC.LIC DataDirect License File
ivtrc28.dll DataDirect trace library
ivtrc28.pdb Debugging symbols for DataDirect trace library
qesqlext.h Header file for DataDirect-specific
ODBC Definitions
\FIXES\:
--------
fixes8.0.txt List of fixes since last release
\help\:
-------
*.html HTML redirects to online connector help systems
and documentation resources
\java\lib\:
-----------
autorest.jar Java components for the driver
\NOTICES\:
---------
ODBC for Autonomous REST Connector
v8.0 notices.txt Third-party vendor license agreements
\READMES\:
----------
ODBC for Autonomous REST Connector
v8.0 readme.txt This file
\restfiles\:
------------
example.rest Example Model file
\samples\bulk\:
---------------
bulk.c Bulk example source
bulk.exe Bulk application
bulk.mak Bulk example make file
bulk.sln Bulk example solution file
bulk.vcproj Bulk example project file
ddlogging.properties Log configuration file for the
Autonomous REST Connector
\samples\bulkstrm\:
-------------------
bulk.cpp Bulk streaming example source
bulk.hpp Bulk streaming example header
bulk.rc Bulk streaming example resource file
bulkstreaming.sln Bulk streaming example solution file
bulkstreaming.vcproj Bulk streaming example project file
bulkstrm.exe Bulk streaming example application
bulkstrm.txt Bulk streaming description
ddlogging.properties Log configuration file for the
Autonomous REST Connector
msgprintf.hpp Bulk streaming example header file
ProgressDataDirect.bmp
ProgressDataDirect.ico
winmain.cpp Bulk streaming example source file
\samples\example\:
------------------
ddlogging.properties Log configuration file for the
Autonomous REST Connector
example.c Example source
Example.exe Example application
example.h Example header
Example.mak Example make file
Example.sln Example solution file
Example.vcproj Example project file
\samples\translat\:
-------------------
LIBMAIN.C
README.TRN Translation Library example description
TRANSLAT.C Translation Library example source file
WINNT.MAK Translation Library example make file
\tools\:
-------
ArcUILauncher.exe Provides access to the Models library
ddextwin.exe License Extender utility
ddprocinfo.exe Processor Information utility
DSNConverterSil.exe Data Source Converter utility
autorestserver32.exe The Autonomous REST Connector SQL
Server Engine
XMLP.exe A GUI demo tool that persists a result set to
an XML data file
\tools\Power BI:
----------------
DataDirectAutoREST.pqx Auto REST Power BI connector file
install.bat Batch file to install Power BI connectors
\tools\Tableau\:
----------------
DataDirect Autonomous REST
Connector.tdc Tableau data source file
\uninstall\:
------------
*.* Files used to uninstall the product
Installed Files for the 64-bit Driver
This file list assumes a full installation of the driver and
documentation.
The installer copies the following file to the Windows system
directory:
ddtrc28.dll DataDirect trace library
The installer copies the following files and subdirectories to the
product installation directory, by default:
C:\Program Files\Progress\DataDirect\ODBC\:
\<install_dir>\:
----------------
license.txt Progress DataDirect license agreement
\drivers\:
----------
ddautorest28.dll DataDirect Autonomous REST Connector
ddautorest28.pdb Debugging symbols for DataDirect Autonomous
REST Connector
ddautorest28r.dll DataDirect Autonomous REST Connector
resource file
ddicu.dll Unicode conversion tables
ddicu.pdb Debugging symbols for ICU library
DDODBC.LIC DataDirect License File
ddtrc28.dll DataDirect trace library
ddtrc28.pdb Debugging symbols for DataDirect trace library
qesqlext.h Header file for DataDirect-specific ODBC
Definitions
\FIXES\:
--------
fixes8.0.txt List of fixes since last release
\help\:
-------
*.html HTML redirects to online connector help systems
and documentation resources
\java\lib\:
-----------
autorest.jar Java components for the driver
\NOTICES\:
----------
ODBC for Autonomous REST Connector
v8.0 notices.txt Third-party vendor license agreements
\READMES\:
----------
ODBC for Autonomous REST Connector
v8.0 readme.txt This file
\restfiles\:
example.rest Example Model file
\samples\bulk\:
---------------
bulk.c Bulk example source
bulk.exe Bulk application
bulk.mak Bulk example make file
bulk.sln Bulk example solution file
bulk.vcproj Bulk example project file
ddlogging.properties Log configuration file for the
Autonomous REST Connector
\samples\bulkstrm\:
-------------------
bulk.cpp Bulk streaming example source
bulk.hpp Bulk streaming example header
bulk.rc Bulk streaming example resource file
bulkstreaming.sln Bulk streaming example solution file
bulkstreaming.vcproj Bulk streaming example project file
bulkstrm.exe Bulk streaming example application
bulkstrm.txt Bulk streaming description
ddlogging.properties Log configuration file for the
Autonomous REST Connector
msgprintf.hpp Bulk streaming example header file
ProgressDataDirect.bmp
ProgressDataDirect.ico
winmain.cpp Bulk streaming example source file
\samples\example\:
------------------
ddlogging.properties Log configuration file for the
Autonomous REST Connector
example.c Example source
Example.exe Example application
example.h Example header
Example.mak Example make file
Example.sln Example solution file
Example.vcproj Example project file
\samples\translat\:
------------------
LIBMAIN.C
README.TRN Translation Library example description
TRANSLAT.C Translation Library example source file
WINNT.MAK Translation Library example make file
\tools\:
-------
ArcUILauncher.exe Provides access to the Models library
ddextwin.exe License Extender utility
ddprocinfo.exe Processor Information utility
DSNConverterSil.exe Data Source Converter utility
autorestserver64.exe The Autonomous REST Connector SQL
Server Engine
XMLP.exe A GUI demo tool that persists a result set to
an XML data file
\tools\Power BI:
----------------
DataDirectAutoREST.pqx Auto REST Power BI connector file
install.bat Batch file to install Power BI connectors
\tools\Tableau\:
----------------
DataDirect Autonomous REST
Connector.tdc Tableau data source file
\uninstall\:
------------
*.* Files used to uninstall the product
~~~~~~~~~~~~~~
February 2026
End of README.TXT