Incident Reports Addressed in 4.18

Incident Reports Addressed in 4.18

The following is a list of the incident reports addressed in version 4.18. Click on the incident # in order to view the details of the incident report.

Serious Problems

Build

#

Title

Workarounds

1	1964	Manually Preparing a Query Causes an AV	No
1	1968	IN Sub-Queries On String Columns Not Working Properly for Arabic Locales	No
1	1970	SELECT COUNT(*) Query Returning Incorrect Results When WHERE Clause Contains Sub-SELECT	No
1	1971	SQL WHERE Clause <> Comparison On Integer Field Returns Incorrect Results	No
1	1974	Application of Cached Updates Can Cause Overwrites of Records Without 8708 Error	No
1	1977	Changing the Active Filter or Range When Cached Updates Are Active Causes Error	Yes
1	1982	Executing a Transaction Rollback on a Table with Newly-Inserted Records Can Cause 10258 Error	No
1	1984	Accessing a BLOB Column From Within a Trigger in the Database Server Causes #9998 Blob Offset Error	No
1	1985	Using <> Filter on a String Field in a Table Without the ANSI Standard Locale Could Hang Application	No
1	1987	<> String Field Comparisons on Tables Not Using ANSI Standard Locale Return Incorrect Results	No
1	1993	<> Filter on Boolean Field Returns Incorrect Results	No

Minor Problems

Build

#

Title

Workarounds

1	1965	DBSYS Reverse-Engineering Generating Incorrect Default Values for Fixed Character Field Types	Yes
1	1975	TDBISAMDatabase KeepTablesOpen Property Not Working Correctly With Exclusively-Opened Tables	Yes
1	1978	RepairTable Does Not Correct Invalid Default Values for BLOB Columns	No
1	1981	Manual Shows Incorrect Example for Optimizing Case-Insensitive Column Comparisons	No
1	1986	Adding a Column Greater than the Total Using the AT Clause in an ALTER TABLE Statement Can Cause AV	Yes
1	1988	Joins Being Executed for JOIN Queries Even Though Driver Table Contains No Records	No
1	1989	Cannot Update a Numeric Column with a NULL Value If a Minimum Value Is Defined for the Column	No
1	1990	Trying to Use a Memo Parameter with a BLOB Column Causes Error	Yes
1	1991	TDBISAMTable GotoCurrent Method Issuing Exception When One TableName Property Has .dat Extension	Yes
1	1992	Using the SQL AVG() Aggregate Function on a BCD Field Returns Incorrect Results	Yes

More Support Options

Search Incident Reports

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals