Caching:

On initial entry to the WORLD Control Panel the Caching tab is displayed:

Local Disk Cache Size - Controls the amount of local disk space allocated to the driver cache.

Enable Schema Cache - Defaults On.  This will cause the schema to be downloaded to the local PC or Server, making subsequent queries much faster during the initialisation phase. However, the first time that a table is accessed will be slower than normal as the cache is written to local disk.

Clear schema Cache - This will clear the local schema cache, thus forcing a refresh back from the server.

Advanced - Logging:

ODBC Debug Logging - Defaults Off.  Switching this feature on will cause the driver to generate detailed level debug logs, something that may be requested by our helpdesk. Refer to the debug logging section of the technical reference to learn how to use this feature.

Logs are generated in the drivers install directory, usually:

C:\Program Files\UES Limited\ODBC Driver\jdeDirectWorld\bin\iwinnt for World and

C:\Program Files\UES Limited\ODBC Driver\jdeDirect\bin\iwinnt for EnterpriseOne/OneWorld as OACLIENT.LOG and OAODBC32.LOG

Using this feature will cause the driver to slow down considerably, please remember to switch logging OFF once you have generated the logs and sent them back to us.

Client Settings:

Select the Client tab

Expose Table Qualifier and Owner - Default is Off.  This may be required by certain applications.

Map UNICODE to ASCII - Default is Off.  Some applications like IBM Domino will not recognise the Unicode data type and will either crash or return a error. Set this switch on when your application does not support Unicode data and is returning a error.

Expose Indexes and Keys - Default is On.  When working with database tables this function displays to the User all Indexes and keys in the table.

Maximum Query Length - Modify the amount of space allocated to the internal variable when sending the SQL statement down to the underlying database.  This may need to be increased if the application you are using is generating very large SQL statements that are being truncated before arriving at the database.