 |  LoginProducts  SalesSupportDownloadsAbout |
| Home » Technical Support » DBISAM Technical Support » Incident Reports » Incident Reports Addressed in 4.22 |
Incident Reports Addressed in 4.22The following is a list of the incident reports addressed in 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 | 2122 | Table Cursors Not Detecting Changes During Manual Refresh With Active Filters and Ranges | No |
| 1 | 2126 | Recursive Join in WHERE Clause Causes Incorrect Results | Yes |
| 1 | 2127 | Database Descriptions Not Being Saved Properly in Database Server | No |
| 1 | 2128 | Using DisableControls While Appending a Record and Updating a Memo Field Causes #8962 Error | Yes |
| 1 | 2134 | Table Can Raise an #8965 Error During Open with Concurrent Delete on the Last Record in the Table | No |
| 1 | 2135 | AfterUpdateTriggers Not Showing the Proper Record Contents if Current Record Falls Out of Filter | No |
| 2 | 2141 | Restricted Transactions Not Acquiring Proper Write Locks During Commit | Yes |
| 3 | 2142 | Navigation with an Active Filter Can Cause Lockup When Other Sessions Rapidly Edit/Delete Records | No |
| 3 | 2143 | Cached Updates Causes #8708 Error on Same Dataset with Different Filtered States | Yes |
| 4 | 2150 | Using NOT Around Join Conditions in WHERE Clause Causes AV | Yes |
| 4 | 2153 | ODBC Driver Raises Error When Used With Visual CE and PocketPC Applications | No |
| 4 | 2154 | SQL INTERSECT and EXCEPT Operators Not Executing Correctly When Combined | No |
| 4 | 2155 | SQL MIN() and MAX() Aggregate Functions Not Handling NULLs Properly with Single-Row Results | No |
| 4 | 2156 | Restricted Transactions Used in UPDATE and DELETE Statements Not Acquiring Proper Write Lock | No |
| 5 | 2158 | DBCMD Server Stops Upon Accepting Connection Under Suse Linux | No |
| 5 | 2160 | Repairing a Table with a Corrupted Index Results in a #9217 Error Reading File Error on the Index | Yes |
| 6 | 2157 | Heavy Updating of Table with BLOB Fields Can Cause #10030 "Invalid BLOB Handle" Error | No |
| 6 | 2163 | Opening Multiple Databases in Server Procedure Can Cause Server Crash on Exit | No |
| 6 | 2165 | Using an ORDER BY on an Aggregate Column Returns Incorrect Results | No |
| 11 | 2129 | Possible Access Violation When Using Custom Functions That Return Currency Values | No |
Minor Problems
| Build | # | Title | Workarounds |
| 1 | 2130 | ZLIBPAS.PAS Unit Contains OutputDebugString Reference | No |
| 1 | 2131 | Cannot Use the ROUND() Function Outside of a SUM() Aggregate Function in an INSERT Statement | Yes |
| 1 | 2132 | Sub-Queries On Tables with Descending Index Matching Selected Column Not Optimized | No |
| 1 | 2133 | ALTER TABLE REDEFINE PRIMARY KEY Not Changing Descending Index Fields to Ascending | Yes |
| 1 | 2136 | Setting a Range and then a Filter Doesn't Change Logical Record Numbers to Reflect Filter | No |
| 1 | 2137 | Incorrect Password Message in DBSYS Utility | No |
| 3 | 2144 | LoadFromStream Not Reporting Progress Correctly | No |
| 4 | 2149 | Using OnFilterRecord That Includes Small Percentage of Records Results in Navigation Errors | Yes |
| 4 | 2151 | Using LASTAUTOINC Function Before a Parameter in INSERT Statement Causes Error | Yes |
| 4 | 2152 | The Administrative Thread Parameter in the DBCMD Database Server is Incorrect | No |
| 5 | 2159 | Using an ESCAPE Character in the Middle of a LIKE Constant Confuses Optimizer | No |
| 5 | 2161 | Using Joined UPDATE Statement Does Not Work for Calculating a Running Total | No |
| 6 | 2164 | Calling TDBISAMTable Locate Method with a NULL Variant for a LargeInt Field Causes Error | No |
This web page was last updated on Wednesday, March 20, 2024 at 07:22 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ?  E-mail us at info@elevatesoft.com |
