A number of problems have recently come to light in AUXORACL and AUXWODBC.
If the array_fetch option was enabled in AUXORACL (which it is by default), spurious records could sometimes be returned by AUXORACL, especially in a call to the pick_record() function (for example in a QAB Window access or multiple choice access). The cause of this problem is that the DP4 program sometimes issues a fetch(PREV), followed by a fetch(NEXT), followed by more fetch(PREV) operations. When the second fetch(PREV) is done AUXORACL attempts to resue the result set generated by the first fetch(PREV). When the array_fetch option is enabled and the first fetch(PREV) had returned the last result (i.e. the first matching record), the second fetch(PREV) should not reuse the result set. However it did, and Oracle returned an error code which was ignored, causing spurious data to be returned to the application.
This bug was present in all the Gateway ADCs. When accessing data using a secondary index, the Gateway ADCs normally add in as extra keys all the parts of the prime key not contained in the secondary index. Unfortunately this was not done for a secondary index corresponding to a primary parent table. As a result fetches on such an index could cause a program to loop and fetch the same record repeatedly. This was most likely to happen in a batch procedure that updated and commited records as it read through the table.
The parameters bound in to such things as the WHERE clauses were bound as INPUT_OUTPUT parameters, whereas they should in fact be INPUT parameters. This has never caused a problem with other ODBC data sources, however SQL Server 2000 generates errors when AUXOWDBC issues such calls. Therefore the parameter type has been changed to use INPUT parameters. There are a number of other problems that may currently prevent SQL Server 2000 from being used as a data source for AUXWODBC. See A4000018 for more details.
If the timestamps=1 option is used to combine data and time fields with matching roles into a single timestamp field on the SQL database, then in the case where one or other field is used in a secondary index, a spurious system error 305 may be generated. This bug is still outstanding.
Where the version affected is given as 4.5xx or 4.6xx, all versions of DP4 issued prior to the date of the fix are potentially affected. Where a specific version number is given the problem was introduced by that release and prior releases are unaffected. If a patch release number is also specified (in parentheses) , the fault was introduced at that specific patch level.
4.522 (2)
AUXWODBC.W32
4.522 (2)
AUXORACL.W32
The download for AUXORACL is encrypted as AUXORACL is not included with the standard DP4 product. Contact us to request the password.
28 Nov 2001 These downloads have been updated to fix the problems descriebd in k4000037
Due to limitations on available web space downloadable fixes are only available for the most commonly used environments, and may not be separately available in both 4.5xx and 4.6xx flavours. If a file you require is not available you can ask us to e-mail it to you.