Incident Reports Addressed in 2.09

Incident Reports Addressed in 2.09

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

Serious Problems

Build

#

Title

Workarounds

1	745	ORDER BY NOCASE Clause with a DISTINCT Query Causes NOCASE to be Ignored	No
1	746	Using a Constant Value for a Float that Exceeds High(Integer) in Filter Expressions Causes Error	No
1	750	Trying to Delete a Record that is Currently Being Edited Causes a Lock Error	Yes
1	762	FlushBuffers Method Not Causing an OS Flush to Occur	No
1	763	Multi-Way INNER JOINs not Working Properly in SQL Engine	No
1	764	Adding an Index, Deleting the Index, Repairing the Table, and then Re-Adding the Index Causes Error	No
1	765	Closing a Table Not Freeing an Internal Structure Causing Exists Function to Fail	No
1	766	Using RestructureIndexDefs.Add Method in Various Orders May Cause Index Creation to Fail	No
1	767	Using an SQL NOT IN Clause with Multiple Columns from Multiple Tables Fails with Error	No
1	768	Using a Long Constant String Value in an SQL INSERT Statement Truncates the Value at 255 Chars	Yes
1	769	Using CopyOnAppend with a DBMemo Control Causes the Memo Field to Not Be Copied to the New Record	No
1	770	Using Multiple OR Conditions in a LEFT OUTER JOIN Clause Does not Work Properly	No
1	772	Using a Nested INNER JOIN within a LEFT OUTER JOIN in a SQL Query Does Not Work Properly	Yes
1	773	Multiple Comments After an SQL Statement Causes an Error	Yes
1	776	Parameters in SQL Containing a SubQuery Cause Query to Return Incorrect Results	Yes

Minor Problems

Build

#

Title

Workarounds

None

More Support Options

Search Incident Reports

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals