Help / Native Connectors/Native Accesses / Native Oracle Connector
  • Overview
  • Configuring a connection
  • Remarks
  • Date format returned by the native Oracle driver (5.5 compatibility)
  • Options of a connection
  • Options for the locks
  • Connection test
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Stored procedures
Configuring the connection with WDORAINS (optional setting)
Native Connectors (Native Accesses)Available only with this kind of connection
For backward compatibility with the earlier versions of Native Oracle Connector (also called Native Oracle Access), the connection can still be configured in WDSQSINS (supplied with Native Oracle Connector). WDORAINS can also be used to configure some specific options of the Native Connector.
It is now recommended to use:
This software is supplied:
  • in 32-bit: WDORAINS.EXE
  • in 64-bit: WDORAINS64.EXE
WDORAINS is no longer required since version 8 (and later).
Reminder: The setting of the connection performed by WDORAINS must be done once only.
This page presents:
Configuring a connection
To configure the connection:
  1. Start WDORAINS (32-bit or 64-bit).
  2. In the window that is opened (used to list the existing connections), click the "Add" button to create a new connection.
    Configuring the data sources
  3. Specify the connection settings:
    Connection description
  • Choose the name of the data source. This name will be passed as a parameter to SQLConnect to connect to the database. If the connection was defined in the data model editor of WINDEV or WEBDEV, specify the name of the corresponding connection.
  • Add a description caption
  • Specify a connection string. This connection string will allow SQL*Net to find the database. This value must be supplied by the administrator of the Oracle database. Example of connection string: "OracleServer". In this example, "OracleServer" is the alias to the server defined in SQL*Net.
  • Specify whether the format of the dates must remain compatible with WinDev 5.5.
    Reminder: Between version 5.5 and version 5.5B, the date format was modified. If you check the box, you will restore the date format returned before version 5.5B (see the paragraph below).
  • Specify the format of the dates for the INSERT and UPDATE queries: this option is used to define the format used by default for the dates in text format. This format will be used if the date format is not specified in the query.
  • Specify the prefetch options for Oracle 8i or later.
    Reminder: Oracle 8i fetches blocks of records ("prefetch"). A large block requires more memory but reduces the network traffic.
    • The number of records corresponds to the number of rows in each block.
    • The maximum memory used corresponds to the size (in bytes) of each block. The "No limit" option allows you to specify no limit.
  • Specify whether the distributed transactions must be used or not. By default, the distributed transactions are used by the locks and transactions handled by Native Oracle Connector. Check this option if:
    • The distributed transactions are not supported by your server.
    • The distributed transactions are not supported by the versions of client libraries (ORA_02041 error).
  • The connection is added to the list once the parameters are validated.


  • The information about the setting is stored in the .INI file in the directory of Windows.
  • WDSQL is used to check whether the connection to the database is correct.

Date format returned by the native Oracle driver (5.5 compatibility)

In version 5.5: The date returned by the native Oracle driver when reading a Date item was: DD-MM-YYYY
In version 5.5B: The date returned by the native Oracle driver when reading a Date item is now: YYYYMMDD.
Reasons behind this modification: Harmonizes the management of dates in WINDEV. Simplifies the assignment of the date read by the Oracle driver in a WINDEV control of DATE type. No specific process is required to convert the date into a format recognized by WINDEV.
How to keep the former operating mode?
Configure the date format in WDORAINS: all you have to do is check "Compatibility: return the dates in 'DD-MM-YYYY' format" when describing the database used.
Reminder: When writing into a database via the native Oracle driver, we recommend that you use the standard ODBC format {d 'YYYY-MM-DD'} (with a space between d and '). The driver automatically converts the date into the format used by the database.
Remark: Starting with version 12, empty dates correspond to strings filled with zeros. In the earlier versions, the empty dates corresponded to empty strings.
Options of a connection

Options for the locks

SQLLock expects two parameters:
  • the timeout: the timeout during the call to SQLLock can be infinite or not (deadlock).
  • the lock mode. For more details, see the documentation about the server.
Options for the locks
Remark: Some failures may occur if the version of the Oracle server is earlier than the version of the Oracle client (Oracle 7.3 server and Oracle 8 client for example). To avoid these problems, check "Always use a 7.x client".
Connection test
To run the test of a connection from WDORAINS:
  1. Select the connection whose test must be run.
  2. Click the "Test" button.
  3. Specify the name and password of the user.
  4. Click "Test connection". The status report is displayed.
    Connection test
Minimum version required
  • Version 9
This page is also available for…
Click [Add] to post a comment

Last update: 04/19/2023

Send a report | Local help