 |  LoginProducts  SalesSupportDownloadsAbout |
| Home » Technical Support » DBISAM Technical Support » Incident Reports » New Incident Reports for 4.22 |
New Incident Reports for 4.22The 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
Minor Problems
Serious Problems
| Build | # | Title | Workarounds |
| 1 | 2141 | Restricted Transactions Not Acquiring Proper Write Locks During Commit | Yes |
| 2 | 2142 | Navigation with an Active Filter Can Cause Lockup When Other Sessions Rapidly Edit/Delete Records | No |
| 2 | 2143 | Cached Updates Causes #8708 Error on Same Dataset with Different Filtered States | Yes |
| 3 | 2150 | Using NOT Around Join Conditions in WHERE Clause Causes AV | Yes |
| 3 | 2153 | ODBC Driver Raises Error When Used With Visual CE and PocketPC Applications | No |
| 3 | 2154 | SQL INTERSECT and EXCEPT Operators Not Executing Correctly When Combined | No |
| 3 | 2155 | SQL MIN() and MAX() Aggregate Functions Not Handling NULLs Properly with Single-Row Results | No |
| 3 | 2156 | Restricted Transactions Used in UPDATE and DELETE Statements Not Acquiring Proper Write Lock | No |
| 3 | 2183 | Using the System RecordID Twice in a Live Query Causes Error 10000 Invalid Field Definition | No |
| 4 | 2157 | Heavy Updating of Table with BLOB Fields Can Cause #10030 "Invalid BLOB Handle" Error | No |
| 4 | 2158 | DBCMD Server Stops Upon Accepting Connection Under Suse Linux | No |
| 4 | 2160 | Repairing a Table with a Corrupted Index Results in a #9217 Error Reading File Error on the Index | Yes |
| 4 | 2163 | Opening Multiple Databases in Server Procedure Can Cause Server Crash on Exit | No |
| 5 | 2162 | Updating a Table via SQL Inside of an AfterDelete Trigger for the Same Table Can Cause Record Skips | No |
| 5 | 2165 | Using an ORDER BY on an Aggregate Column Returns Incorrect Results | No |
| 6 | 2166 | IS NULL and Other Extended Binary Operators Not Working Properly in UPDATE Statements | No |
| 6 | 2168 | IF() Function That Refereces Multiple Tables in Join Expressions Causes Incorrect Results | Yes |
| 6 | 2173 | Updating BLOB Fields During an Edit Can Cause Record Contents to Revert Back to Original Values | No |
| 6 | 2174 | Using Aggregate Expressions in SELECT Statement With UNION/INTERSECT/EXCEPT Causes Error | No |
| 6 | 2177 | Boolean Parameters Not Working Properly in SQL Queries | No |
Minor Problems
| Build | # | Title | Workarounds |
| 2 | 2144 | LoadFromStream Not Reporting Progress Correctly | No |
| 3 | 2149 | Using OnFilterRecord That Includes Small Percentage of Records Results in Navigation Errors | Yes |
| 3 | 2151 | Using LASTAUTOINC Function Before a Parameter in INSERT Statement Causes Error | Yes |
| 3 | 2152 | The Administrative Thread Parameter in the DBCMD Database Server is Incorrect | No |
| 3 | 2167 | Using SetRange without Setting Any Field Values Causes Incorrect Information in Ranged Property | Yes |
| 3 | 2169 | Server-Side Procedure Descriptions Not Being Saved Properly | No |
| 4 | 2159 | Using an ESCAPE Character in the Middle of a LIKE Constant Confuses Optimizer | No |
| 4 | 2161 | Using Joined UPDATE Statement Does Not Work for Calculating a Running Total | No |
| 5 | 2164 | Calling TDBISAMTable Locate Method with a NULL Variant for a LargeInt Field Causes Error | No |
| 6 | 2175 | Comparing an Invalid Word Value to a Word Column Causes Incorrect Results | Yes |
| 6 | 2176 | Corruption in the Last Record ID for a Table Is Not Fixed by RepairTable | No |
| 6 | 2178 | Closing a TDBISAMTable or TDBISAMQuery During Edit with Attached TDBMemo Controls Causes AV | Yes |
This web page was last updated on Tuesday, April 23, 2024 at 08:39 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ?  E-mail us at info@elevatesoft.com |
