New Incident Reports for 2.10

New Incident Reports for 2.10

The following is a list of the new incidents reported for version 2.10. Click on the incident # in order to view the details of the incident report.

Serious Problems

Build

#

Title

Workarounds

1	805	Using a Const=Const Expression Combined with OR Operator in SQL WHERE Clause Causes Incorrect Result	No
1	806	Using an Un-Optimized <= Comparison in SQL WHERE Clause Expression Causes Incorrect Results	Yes
1	807	Using a NULL Value in SQL IF() Function Call Causes Error	Yes
1	808	Using Nested LEFT OUTER JOINs in SQL SELECT Statement Causes Incorrect Result	No
1	810	Running Live SELECT SQL w/ Calc Fields, Editing Record, and then Running a DELETE SQL Causes Error	No
1	811	Partial Match with NOT LIKE Operator in SQL Un-Optimized WHERE Expression Causes Incorrect Results	Yes
1	814	Changing Field Names or Descriptions and Adding or Removing Indexes Causes RestructureTable Problem	No
1	817	Using an Embedded Asterisk in an SQL Comment Causes an Error	Yes
1	821	Using LoadFromStream from within Multiple Threads Causes a Lockup	No
1	832	Un-Optimized SQL WHERE Clauses Containing the Target Table of an INNER JOIN are too Slow	Yes
1	912	Using a Constant on the Left Side of a Binary Operation in SQL or Filter Causes Incorrect Result	Yes

Minor Problems

Build

#

Title

Workarounds

None

More Support Options

Search Incident Reports

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals