Icon New Incident Reports for 2.06

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

Serious Problems


Build#TitleWorkarounds
1706DBSYS SQL-92 Reverse Engineering Not Working Properly for Tables Without a Primary IndexNo
1707Including a BLOB Column in a SQL SELECT Query with a GROUP BY Clause Causes #8708 ErrorNo
1708Queries and Filters on Tables Using a Non-English or ANSI Language Driver Return Incorrect ResultsNo
1710UpgradeTable Method Failing with Access Denied Error Message When Table Should Be ClosedNo
1711Using NOAUTOINC with an SQL INSERT Statement That Uses a SELECT Statement Does NothingNo
1712Using Suppression of AutoInc Values and Editing AutoInc Values Causes Error on Delete of Same RecordNo
1714DELETE and INSERT SQL Statements Causing Error with COMMIT INTERVAL ClauseNo
1715RowsAffected Property Incorrect For INSERT, UPDATE, or DELETE Queries that are Implictly Rolled BackNo
1716Using Locate Method on Query Result Sets Returns Random ResultsNo
1717Compiling an Application with Range Checking Turned On Causes Range Errors When Table Opens FailNo
1718Using Non-Join Expressions in SQL JOIN Conditions Causes Incorrect ResultsNo
1719Locate Method of TDBISAMTable Not Working Properly After Record is Just AddedNo
1720Min/Max/Default Validity Checks for SmallInt Fields Not Being Transferred ProperlyNo
1721Using Locate to Do a Partial-Key Search on The Active Index When No Records Exists Causes ErrorNo
1725Using CopyOnAppend Property Can Cause BLOB Corruption After AppendNo
1727DBSYS Reverse-Engineering Process Always Sets Last AutoInc Value Even if Not Adding Existing DataYes
1728Using a Column Name in SQL HAVING Clause When Column Is Aliased Causes AVYes
1762FlushBuffers Method Not Causing an OS Flush to OccurNo
1773Multiple Comments After an SQL Statement Causes an ErrorYes

Minor Problems


Build#TitleWorkarounds
None

Image