HiT Software Open up your Data
Buy Download Contact Us

Chinese Website 
Japanese Website 


Support
Technical Support
Knowledge Base
Customer Portal
Release History/Notes
Update Packs
FAQs
Release Notes

HiT ODBC/400 and HiT ODBC Server/400 Release Notes
 
Version
Date
Changes

8.0.0.0

 

10/22/07
  • Added support for Microsoft Windows Vista and passed Windows Vista certification;
  • Added support for special characters in the parser;
  • Added support in the LITE version to execute stored procedures;
  • Introduced HTML help to replace WinHelp.

7.0.0.5

 

09/02/05
  • Fixed a problem where HiT Server Manager was not included in the HiT ODBC Server/400 releases.

7.0.0.4

 

08/12/05
  • Added a workaround to completely disable Query Timeout (CommandTimeout) settings (Add a minus sign (-) to the value set in the Communications tab Timeout Value field (data source configuration dialog);
  • Modified update pack setup to enable updating of ODBC/400 when installed with DB Moto;
  • Added support in the data source configuration General Tab to use the specified host code page to override column CCSIDs during character conversion;
  • Added support in the data source configuration General Tab to use the specified host code page to override catalog CCSIDs during character conversion;
  • Fixed a problem where Excel Macros kept opening unnecessary new connections. The DATABASE token is no longer removed in the SQLDriverConnect output string when it was specified in the original connection string;
  • Fixed a compatibility problem with Windows 2003.
7.0.0.1
Update Pack Only
09/21/04
  • Updated SSL libraries with the latest cipher suites.
7.0.0.0
07/27/04
  • Added support for i5/OS V5R3;
  • Improved performance when working with OS/400 V4R5, especially for INSERT/UPDATE/DELETE statements;
  • Added support for LOB data types of small size (the length is between 1 and 32KB) where the LOB locator cannot be used to reference the LOB value;
  • Added full support for CommandTimeout: its value was not properly used and the timeout for the command was set to the iSeries/AS400 job’s query timeout;
  • Fixed a limitation in the parser: a ‘case’ expression was not supported inside a ‘date’ function;
  • Fixed a problem where Call Statements with mixed SBCS and DBCS characters were truncated because the number of shift bytes was ignored;
  • Fixed a problem where the blanks at the end of a double byte string were removed even if the RemoveBlanks check was not enabled;
  • Updated the SSL support with the latest cipher suites;
  • Fixed a problem in DECIMAL data retrieving: length instead of scale was used to calculate the value to retrieve. In many cases, that caused values to be returned as 0 when length was > scale.
6.1.2.9
Update Pack Only
12/12/03
  • Added a new option in the Data Source General tab to enable the driver to override the CCSID settings for the Catalog functions. Setting the checkbox forces the driver to use the connection CCSID instead of the column CCSID when performing a Catalog function; this allows the user to use some non-standard characters for tables/columns names;
  • Fixed a problem with Cognos Impromptu that sets the driver in read-only mode before running a stored procedure;
  • Fixed a problem with ADO retrieving NUMERIC/DECIMAL fields using GetRows method (recordset);
  • Fixed a regression in EbcdicToAnsi conversion that freezes an application when it retrieves UCS2 fields;
  • Fixed a problem where SQLGetTypeInfo for Sql_Decimal returned "length,scale" instead of "precision,scale" in the CREATE_PARAMS column;
  • Fixed a problem where the AllowPackageUpdate connection property was set always to true (the default value) in the connection parameters.
6.1.2.8 08/06/03
  • Added support for BIGINT data type. Now the driver fully supports the 64bit length integer values;
  • Improved Columns catalog performance. SQLColumns has been improved to perfom better and faster;
  • Improved High-level trace. API exit time has been added to the trace.
6.1.2.7
07/14/03
  • Improved high level trace. Output parameters are now correctly traced after the execution of a statement;
  • Fixed erroneous column length for PACKED/DECIMAL as described in catalog SQLColumns. The column size was returned instead;
  • Fixed wrong column length for column COLUMN_NAME in result set description for catalog API SQLColumns. The name was truncated to be 4-char long;
  • Improved low level error management in multi-threading mode;
6.1.2.5
06/10/03
  • Fixed problem in UCS2 fields management : Can now read and write correctly into UCS2 fields;
  • Fixed a problem in DPC Support that caused failures in the connection to the server;
  • Fixed a problem in EBCDIC to ANSI conversion related to conversion tables loading;
  • Low level trace improvement : Process ID, Thread ID and timing are now traced;
  • Added a workaround in stored procedure management: The driver exits with no errors or warnings when the OS/400 returns a warning about the numbers of recordsets returned by the SP execution;
  • Fixed a sporadic parser problem with CREATE TABLE statements and PRIMARY KEY columns: Sometimes the PRIMARY KEYS qualifier would be skipped;
  • Removed "Host System Name" entry in DSN configuration (only for TCP/IP Native connection).

6.1.2.4

04/14/03
  • Added Parameters CCSID management: now the EbcdicToAnsi & AnsiToEbcdic are performed using the conversion table related to CCSID parameter;
  • Improved performance in column CCSID management;
  • Fixed a bug related to column with 64K CCSID : The SQLColumns now returns the right data type if the Convert 64K CCSID option is enabled;
  • Improved SQLColumns management. The columns list is returned in the creation order;
  • Fixed memory leaks in low level trace file management;
  • Fixed concurrency problems in error management;
  • Improved Performance in RLE Compression Management;
  • Added RLE Compression for AS/400 hosts older than V5R1 (starting from V4R3);
  • Improved handling of SQL stored procedure and external stored procedure user-defined error codes. Specific errors code (return code) are also returned;
  • Logon Dialog now prompts TOPMOST even if the calling application is not focused (i.e. DB2Motion -> add new Source AS/400 DSN);
  • Introduced full BOS Router support using DPC – BOS were recognized by DBMS server but not by DPC server; low level traces, when tracing DPC stuff, appeared to be not complete because of an “unknown router” setting. Possible workaround: setting NS Router instead of BOS allowed DPC support to work fine;
  • Fixed: Checking a statement to verify if it's called by the bridge was increasing a pointer without checking for its length, causing an unhanded exception.


6.1.2.1
01/31/03
  • Fixed a regression in the management of SQL Columns that causes a C++ Unhandled Exception : ordinal position must be retrieved starting from V5R1;
  • Fixed an error on calling a query on the same library as the user, the library would be substituted with the DSN connection library;
  • Added Remarks Support : now SQLColumns returns the field’s descriptions stored in AS/400 catalog;
  • Added “trace on the fly” feature, to start and stop traces ( global and/or low level traces) when a process is running;
  • Fixed a problem related to retrieving data with SBCS only CCSID under a connection performed using DBCS ccsid;
  • Fixed and improved optimistic approach support for positional queries (i.e. DAO) for adding and positioning field. Fixed “Statement inserts or updates wrong number of values.” problem;
  • Fixed a problem related to optimistic approach support for positional queries and positioning option (The problem is sporadic and it is happened in DB2/Motion when the AS/400 is the source and no primary key is defined in the table : the data were not returned correctly while doing select statements through DAO );
  • Added RLE Compression Support for V5R1 Hosts;
  • Fixed an error with Arabic conversion in multi-connection cases;
  • Fixed Arabic conversion based on single column CCSID;
  • Fixed an error in optimistic update using DAO, some parameters were not passed through the descriptor.
6.1.1.0 12/17/02
  • Improved performance regarding the communication with OS/400 through ODBS;
  • Fixed a problem with SQLCloseCursor, occasionally under certain conditions the driver returned an unexpected error;
  • Fixed a sporadic problem which occurs when exiting from a NT service that involves HiT ODBC driver (Unhandled exception : Access Violation);
  • Fixed an error on parsing statements containing double quotes on the table name when using a DBCS codepage.

6.1.0.8

10/25/02
  • Fixed problems in the management for Graphics and VarGraphics DBCS only field;
  • Fixed a problem with Two Phase Commit Support: When in a distributed transaction only xa_commit has to be sent;
  • Added the following HSTABLEs : 833 (Korean SBCS), 28709 (Traditional Chinese SBCS), 300 (Japanese DBCS).
6.1.0.7 10/10/02
  • Fixed a problem in column CCSID management : When column CCSID is not supported, the driver now uses default CCSID;
  • Fixed a problem in large trace files management : sometimes traces didn't start;
  • Fixed a few problems regarding mouse events inside the toolbox.
6.1.0.6 09/19/02
  • Info retrieved by catalog for XXXGRAPHIC data types modified to emulate Client Access Express behavior: such data types are no more described as “BINARY” but directly as “GRAPHIC”;
  • HiT ODBC Server/400 for DB2Motion now can be used via ODBC TEST;
  • EBCDIC Cyrillic support (1025) is now available along with its HSTABLE.

6.1.0.5

09/12/02
  • Modified the parser to allow the use of functions in the GROUP BY clause;
  • Fixed a lock problem during execution of parametric distributed program call;
  • Introduced UCS-2 support for CCSID 13488 data and for GRAPHIC data types;
  • Global trace timing introduced

6.1.0.4

06/05/02

  • Fixed a problem with IIS: when the session timed out, the thread in IIS that was running the ASP page that created the HiT Object was killed;
  • HiT ODBC Server/400 for DB2Motion now recognizes the new DB2MOTIONJOURNALDIAG utility;
  • Fixed an error in creating UPDATE statement for positional updates.

6.1.0.3

05/20/02

  • Modified optimistic approach support for positional queries (i.e. DAO) to handle case sensitive field names.

6.1.0.2

05/06/02

  • Modified optimistic approach support for positional queries (i.e. DAO) to handle case sensitive table/library names;
  • Introduced a structured management in using HSTABLEs: sometimes a delay is needed because concurrent threads can access the same table at the same time, returning “ODBS error: Conversion table not found” errors;
  • ODBC for DB2Motion now sets the DATABASE token in the output connection string and recognizes the new CHGJRNRCV.EXE utility.

6.1.0.1

05/02/02

  • Modified LITE version: changed the maximum connection number tracking system to work for environment instead than for module. Basing the maximum number of connections on the environment allows an increased number of connections to be available for applications using multiple environments like MS Access 2000;
  • Fixed a problem in fields conversion using CCSID: now the driver does it instead of OS/400;
  • Fixed an error with ExtendedFetch, some records were not processed in the SELECT.

6.1.0.0

04/03/02

  • Added support for ‘CASE expressions’ inside select statement;
  • Added TWO PHASE COMMIT management ( V5R1 or higher version of OS/400).
  • Fixed a problem when freeing environment handle.
  • Fixed a problem in parsing SQL Statement : now case sensitive identifiers are processed correctly.
  • Fixed a problem running Stored Procedures with NULL output parameters.

6.0.0.13

03/15/02

  • Fixed a problem in Convert CCSID 65535;
  • Fixed a problem with parser for Insert statement with scalar function.

6.0.0.12

03/06/02
  • Fixed a bug in switching between different conversion tables (in particular running DB2Motion).
6.0.0.11
03/04/02
  • Introduced optimistic approach support for positional queries (i.e. DAO);
  • The output string provided by SQLDriverConnect when connecting in NOPROMPT mode contains the “DATABASE” token.
6.0.0.10
02/21/02
  • Fixed a problem with Absolute Orientation during Extended Fetch;
  • Now it is possible to execute Remote Command Call with the following syntax : {{ command }}
  • Fixed a problem retrieving error messages while executing Remote Program Call
  • Fixed a problem with SQL Statements produced with Microsoft Access 97 running on WINNT (Changed SQL Statement Pre-Parsing management).
6.0.0.9
02/02/02
  • Fixed a problem with SQL Statements length;
  • Fixed the start problem of the low traces;
  • Fixed a problem with thick client and Access97 to link a table: the configuration parameters in some cases weren't counted correctly.

6.0.0.8

12/04/01

  • Fixed a problem with the driver not working properly when Crystal Reports 8 set the driver to read-only before calling a stored procedure. Now, for Crystal Reports only, we allow calling a stored procedure even if the setting is read-only.
6.0.0.7 11/29/01
  • Fixed a conversion problem using a SQL_C_NUMERIC type with precision greater then 19: the conversion routine gave an incorrect value fetching the data;
  • Fixed a problem with CALL STATEMENT using Query Analyzer (SQL Server) and MS ODBC bridge: it is now possible to run this kind of statement;
  • Fixed an error during repeated insertions of timestamp values;
  • Inserting a wrong TIME value resulted in inserting a ’00:00:00’ value, instead of getting the error.
6.0.0.6 10/19/01
  • Fixed a synchronization problem detected with Microsoft Web Application Stress Tool running a number of threads greater then 1;
  • Added “DB2 Motion” Integration with HIT ODBC/SERVER;
  • Fixed a problem (in debug mode): if the connection failed, another error were thrown caused by the notification to the agent of the ending of the connect function.
6.0.0.5 07/30/01
  • Fixed a problem with extended fetch using move (n) with ADO;
  • Fixed a problem with extended fetch using Query Analyzer (SQL Server) and MS ODBC bridge: only a row was returned from a query;
  • Added support for Ordinal Position (version V5R1 or higher);
  • Removed constraint to 256 parameters as maximun number of parameters for a SqlBindParameter;
  • Added support for SQLPrimaryKeys and SQLForeignKeys functions;
  • Adjusted some code for increase performance;
  • Solved a problem with Delphi 5 using Database Explorer with SqlGetData;
  • It’s now possible upgrade HiT ODBC Server/400 version 5.0 to version 6.0.
6.0.0.4 04/26/01
  • Solved a problem with connection pooling: some data for the connection weren’t saved correctly;
  • Fixed a problem about key validation during setup: old keys HiT ODBC/400 version 5.1 were verified also installing version 6.0.
  • Changed the VB toolkit version number.
6.0.0.3 04/10/01
  • Fixed a problem that occurs with winsock when running on Windows 95/98 allowing you to install the HiT Server Manager without updating winsock on your system.
6.0.0.2 03/19/01
  • Added HiT Server Manager to HiT ODBC Server/400 to provide services for monitoring server activity and connection pooling;
  • Added support for large binary objects: BLOB and CLOB;
  • Added Change License Key menu item to Toolbox for updating product license keys;
  • Modified uninstall program to allow users to choose whether to keep or delete data sources when removing the product;
  • Updated installation to include Microsoft Data Access Components (MDAC) version 2.6;
  • Corrected an error caused by opening conversion tables in unshared mode.
5.1.3.3
11/29/00
  • Fixed a problem with HiT SignOn component on Windows 95/98 platforms: the taskbar icon was visible but did not receive mouse messages.
5.1.3.2 10/24/00
  • Fixed problem associated with catalog queries: a wrong type size in binding fixed-length types with SQLBindCol. For instance, reading a SMALLINT data type, it called SQLBindCol specifying a 4-byte long buffer (instead of 2 bytes) for a smallint. The driver “trusted” the application and returned data for the specified bound buffer, causing missing data.
5.1.3.1 10/12/00
  • Modified error messages due to invalid key and added expiration date and max number of connections into the About dialog in the Toolbox;
  • Added a feature to resolve queries containing column aliases in the SELECT clause, but referring to them by the column name (and not by alias) in the ORDER BY clause: the query parser has been modified in order to send the correct query to the server;
  • Fixed a problem with HSSignOn object: if User ID caching wasn’t used we were having an unhandled exception problem in deallocating the driver (the problem was not present by checking the User ID caching option).
5.1.3.0 08/18/00
  • Fixed a problem with SQLColumns returning Unhandled Exception when working with V4R3M2. This is related to HSODBS32.DLL only.
  • Fixed a problem where a warning during Fetch in ODBS was treated as an error.
  • Fixed a problem where sometimes EBCDIC data was not converted to ASCII when running a catalog query or a select query. This happened because the AS400 Optimized Server sometimes returns wrong information about the number of rows returned.
  • Forced non-compressed mode in ODBS connection attributes because some customers experienced compressed/uncompressed data stream problems.
  • Fixed a problem with C++ and the CRowset class when using Dynamic cursors.
  • Modified behavior with MS Access 2000 when opening linked tables. MS Access provided the most recently used UID, so it appeared as inactive. Now it’s possible to change the user ID.
  • Fixed a minor Fetch problem when using SQLExtendedFetch with SQLGetTypeInfo that was found using MS Project 2000.
  • Fixed a small parse problem when using double quoted identifiers with ORDER BY clauses.
  • Introduced HiT SignOn component to cache User ID and Password information with data sources when Use UserID Caching is enabled during data source configuration.
5.1.2.2 06/30/00
  • Fixed a problem with SQLColAttribute where the value 6 was returned for SQL_DESC_OCTET_LENGTH option intead of 16 when the SQL type is SQL_TIMESTAMP.
  • Modified HSTABLE.875 (Greek)
5.1.2.1 06/16/00
  • Fixed a small problem in the global trace – NULL and SQL_NULL_DATA hexadecimal addresses were not correct in SQLBindParameter tracing.
  • Increased SQL ODBS string size to 32767 bytes. Previously it was 4096 and might cause truncation if the SQL string size was bigger. The maximum SQL string size for V4R4 ODBS Server is 32767.
  • Fixed a problem with stored procedure calls returning output parameters and result sets. If the result sets were not downloaded and the query was prepared and executed many times, there were problems because the parameter descriptors were overwritten by the result set columns descriptors.
  • HSTABLEs 420 – Arabic and 838 – Thai added to the tables list.
  • Modified Toolbox behavior to disable all traces when closed.
  • Fixed a problem with SQLColAttribute where it was returning a 4-byte integer value even when the SQL_DESC_ option is a 2-byte value. This could cause problems when returning negative values, in particular with SQL_DESC_TYPE.
  • Fixed a problem with SQLColAttribute where it was returning a length value in StringLengthPtr for string attributes (i.e. SQL_DESC_NAME) even if the string buffer CharacterAttributePtr is empty. Also fixed SQLGetDescField with the same attributes.
  • Fixed a problem with SQLGetTypeInfo where MAXIMUM_SCALE and MINIMUM_SCALE values were returned in 2- byte integer values but some applications like Cognos Impromptu provide 4-byte buffers for such values
5.1.2.0 05/02/00
  • Modified the global trace to give more details about the system running the driver, the HiT product installed and the MDAC version.
  • Fixed a problem in using the driver with Visual FoxPro where the result set description was not returned when getting SQL_SUCCESS_WITH_INFO after a SELECT.
  • Added support for function LOCATE.
  • Released support for strong encyption using for all versions.
  • Updated the MDAC version (2.50.4403.12) available during setup.
5.1.1.1 02/01/00
  • Introduced a RW and RO version for BOS.
  • Changed the maximum connection number check to work by module rather than by environment. Basing the maximum number of connections on the environment caused an increased number of connections to be available for applications using multiple environments.
  • Removed the DATABASE token in the SQLDriverConnect output string. This caused problems with MSQuery or Excel using simple DSNs. HiT ODBC/400 can run multiple queries prompting for a new connection only once because the output string provided by SQLDriverConnect uses DSN, UID and PWD tokens only. Adding any other token causes MSQuery to prompt every time it is asked for a new query and create a completely new connection.
5.1.1.0 01/24/00
  • Introduced a dbXpress feature.
  • Added FileDSN test, view and dbXpress options to the Toolbox
  • Fixed a problem for DBCS versions on Windows systems running the RichWin product. There were problems in character conversion for systems running RichWin with locale option (a RichWin option not available in Win 9x versions) disabled. In Win 9x versions the RichWin locale default is set to 0.
  • Fixed a minor bug introduced in version 5.1.0.2. A side effect of this problem is that when using SQL_C_DEFAULT as a C type in SQLBindCol, the bound buffer size was changed to 0 giving truncation problems.
  • Fixed a problem when using a linked server with Microsoft SQL Server (through “Microsoft OLE DB Provider for ODBC Drivers”). When “Use dbXpress” was checked, there were problems in executing a select statement on a table in the linked server. The error message was: Error 7357. Could not process object 'xxx'. The OLE DB provider 'yyy' indicates that the object has no columns.
  • Updated conversion tables 280 and 37;
  • Introduced Performance Tab in the data source configuration and changed the position of some entries.
  • Added a License key field in the “About” dialog of the Toolbox.
  • Modified the setup so that the runtime version can only be installed on machines with Microsoft Windows 95/98, Windows NT3.51 or NT4.0 Workstation and Windows 2000 Professional (Windows 3.11 if you are using the 16-bit version of ODBC/400).
  • Setup: Changed installation directory (HitODBC400);
  • Setup: Changed installation options into installation option dialog;
  • Setup: Dcom 98 replaced from Dcom95 latest version (1.3).
5.1.0.4 12/14/99
  • Introduced Symbiator version;
  • Updated conversion table 937;
  • SQLDriverConnect failed during connection SQL_DRIVER_NOPROMPT when the buffer length was lower than length of connection string.
5.1.0.3 12/07/99
  • Fixed CHAR conversion problem in parametric queries for DBCS code page (SBCS param. queries with CHAR data worked fine)
  • Fixed 16 bit Standard driver CREATE INDEX syntax: using qualified table names in the ON clause (CREATE INDEX … ON LIB.TAB…) caused a syntax error. Unqualified syntax worked fine.
  • Fixed problem revealed by PowerBuilder: PB used a wrong type size in binding fixed-length types with SQLBindCol. For instance, reading an INTEGER data type, it called SQLBindCol specifying a a 52-byte long buffer (instead of 4 bytes) for an integer. The driver “trusted” the application and returned data for the specified bound buffer, causing missing data. Now we automatically use fixed-length bound values for fixed-length data types.
  • Fixed a SQLConfigDataSource problem: using this API to create a new DSN programmatically caused new DSN info come into garbage (the sequence in which DSN tokens were used wasn’t correct).
  • SQLGetInfo returns now Client Access’ driver name (SQL_DRIVER_NAME option) when called by Seagate Crystal Report in order to let CR call HiT driver using native LEFT OUTER JOIN syntax instead of standard ODBC LOJ syntax (BTW, the ODBC LOJ syntax generated by CR was syntatically wrong!)
  • Fixed Cognos Impromptu/HiT LITE problem: Impromptu makes us of SQLGetInfo SQL_DEFAULT_TXN_ISOLATION value in order to set a transaction isolation level (related with DSN Isolation Level). ODBC spec clarifies that a driver not supporting transactions must set this value to 0 (and LITE driver cannot support transactions because it’s read-only) and that’s the value returned by LITE driver; transactionable drivers (read-write) return values 1-2-4-8 for this SQLGetInfo. Impromptu ignores ODBC specs and use this SQLGetInfo to set the connection attribute SQL_ATTR_TXN_ISOLATION using SQLSetConnectOption/SQLSetConnectAttr which allows ONLY > 0 values (you set this value ONLY if you need to run transactions – but LITE cannot do that!). In the LITE case, this value was set to 0 and the Driver Manager refused it reporting an “Invalid argument value” error.
5.1.0.2 10/14/99
  • New setup versions: Weak and Strong;
  • Modified handling of error connection list. The list wasn’t reset after connection failed.
5.1.0.0 09/28/99
  • Introduced SSL security with two level ( DES40 = Weak Encryption e 3DES = Strong Encryption) only with native TCP/IP as communication protocol;
  • New MDAC version (2.1.2.4202.3);
  • New version with Strong Encryption for USA.
5.0.1.5 07/29/99
  • Modified AnyNet DLL – the mode name wasn’t correctly set and was passed always QPCSUPP;
  • Setup disables MDAC component on windows 2000;
  • Administrator icon created if MDAC component is checked during setup.
5.0.1.4 07/08/99
  • Introduced User ID Caching. The driver stores a password map of user who successfully connected at least one time. Setting the check "Use UserID Caching" in the Advanced Tab is possible reconnect using SQL_DRIVER_NOPROMPT, SQL_DRIVER_COMPLETE, SQL_DRIVER_COMPLETE_REQUIRED as completion parameter in SQLDriverConnect and passing only the name of DSN or fileDSN;
  • Updating help and context help files;
  • Update readme and inserted version number;
  • Inserted MDAC & DCOM98 that replace Microsoft ODBC installation;
  • New versions:
  • LITE version (without “silent.exe” and with a different “setup.iss”);
  • WEB version (standard version without MDAC and DCOM).
5.0.0.3 06/02/99
  • Updating context help for the host code page field;
  • Modified the look of the controls of the data tab to better browse the code page info.
5.0.0.2 05/28/99
Fixed the problem with Toolbox: the low level trace file name was used as global trace file name in some situations: using Toolbox, passing from a form to another with this sequence:

Config. Global Trace Mask – (set active) – Ok

Config. Low Level Trace Mask – (set active) – modify low level trace file name – Ok

Reopen Config. Global Trace Mask.

At this point the global trace file name and low level file trace were equal. Choosing Ok both names were confirmed as equal;

Fixed problem with varchar null fields with parametric query. In some cases, if there was a null field before the last field there was an error with insert parametric queries. It happened exporting tables with null fields from Access.

Complete syntactic support for queries containing scalar functions called with standard ODBC syntax:

{fn <function and relative parameters>} or

{FN < function and relative parameters >}

Before this it was supported only function calls using standard SQL syntax or native AS/400 that didn’t accept “fn” and “{“ ” }”

On windows system NT 3.51 setup installs the correct DLL that solves problem with context help;

Solved problem with mainhelp: during data source configuration the topic wasn’t found;

Modified expired password change support – now the change password mask is activated immediately if the connection is not NOPROMPT.

5.0.0.1 05/11/99
  • Fixed a problem with params "AT EXEC"; it crashes MS Access when using LONG VARCHAR fields which force MS Access to use params "AT EXEC" via SQLParamData/SQLPutData. The problem was also retrieved when such fields via RDO in VB modifying such data types with parametric UPDATE queries.
5.0.0.0 05/04/99
  • New features: ODBC 3.0;
  • Introduced positional update features for SQLSetPos (SQL_UPDATE, SQL_DELETE) and SQLBulkOperations (SQL_ADD);
  • Management of trailing blanks for char data; can hold opened cursors during commit/rollback; can use unqualified table names with *SYS syntax;
  • Expired password handling: if the user password is correct but expired (and if the prompt option has been correctly set), the application’s front-end will be prompted with a new dialog box to change the expired password (similarly to what Client Access does). The user has to provide the old and the new passwords;
  • Silent setup: to install HiT ODBC/400 without user intervention, the “silent.exe” file was added to the installation. Silent.exe is called from the command line.


 


All Rights Reserved © 2008 HiT Software, Inc.
All other trademarks or registered trademarks herein are the property of their respective owners.