Icon New Incident Reports for 4.22

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

Serious Problems

12141Restricted Transactions Not Acquiring Proper Write Locks During CommitYes
22142Navigation with an Active Filter Can Cause Lockup When Other Sessions Rapidly Edit/Delete RecordsNo
22143Cached Updates Causes #8708 Error on Same Dataset with Different Filtered StatesYes
32150Using NOT Around Join Conditions in WHERE Clause Causes AVYes
32153ODBC Driver Raises Error When Used With Visual CE and PocketPC ApplicationsNo
32154SQL INTERSECT and EXCEPT Operators Not Executing Correctly When CombinedNo
32155SQL MIN() and MAX() Aggregate Functions Not Handling NULLs Properly with Single-Row ResultsNo
32156Restricted Transactions Used in UPDATE and DELETE Statements Not Acquiring Proper Write LockNo
32183Using the System RecordID Twice in a Live Query Causes Error 10000 Invalid Field DefinitionNo
42157Heavy Updating of Table with BLOB Fields Can Cause #10030 "Invalid BLOB Handle" ErrorNo
42158DBCMD Server Stops Upon Accepting Connection Under Suse LinuxNo
42160Repairing a Table with a Corrupted Index Results in a #9217 Error Reading File Error on the IndexYes
42163Opening Multiple Databases in Server Procedure Can Cause Server Crash on ExitNo
52162Updating a Table via SQL Inside of an AfterDelete Trigger for the Same Table Can Cause Record SkipsNo
52165Using an ORDER BY on an Aggregate Column Returns Incorrect ResultsNo
62166IS NULL and Other Extended Binary Operators Not Working Properly in UPDATE StatementsNo
62168IF() Function That Refereces Multiple Tables in Join Expressions Causes Incorrect ResultsYes
62173Updating BLOB Fields During an Edit Can Cause Record Contents to Revert Back to Original ValuesNo
62174Using Aggregate Expressions in SELECT Statement With UNION/INTERSECT/EXCEPT Causes ErrorNo
62177Boolean Parameters Not Working Properly in SQL QueriesNo

Minor Problems

22144LoadFromStream Not Reporting Progress CorrectlyNo
32149Using OnFilterRecord That Includes Small Percentage of Records Results in Navigation ErrorsYes
32151Using LASTAUTOINC Function Before a Parameter in INSERT Statement Causes ErrorYes
32152The Administrative Thread Parameter in the DBCMD Database Server is IncorrectNo
32167Using SetRange without Setting Any Field Values Causes Incorrect Information in Ranged PropertyYes
32169Server-Side Procedure Descriptions Not Being Saved ProperlyNo
42159Using an ESCAPE Character in the Middle of a LIKE Constant Confuses OptimizerNo
42161Using Joined UPDATE Statement Does Not Work for Calculating a Running TotalNo
52164Calling TDBISAMTable Locate Method with a NULL Variant for a LargeInt Field Causes ErrorNo
62175Comparing an Invalid Word Value to a Word Column Causes Incorrect ResultsYes
62176Corruption in the Last Record ID for a Table Is Not Fixed by RepairTableNo
62178Closing a TDBISAMTable or TDBISAMQuery During Edit with Attached TDBMemo Controls Causes AVYes