 |  LoginProducts  SalesSupportDownloadsAbout |
| Home » Technical Support » DBISAM Technical Support » Incident Reports » Incident Reports Addressed in 4.03 |
Incident Reports Addressed in 4.03The following is a list of the incident reports addressed in version 4.03. Click on the incident # in order to view the details of the incident report.
Serious Problems
Minor Problems
Serious Problems
| Build | # | Title | Workarounds |
| 1 | 1505 | Using TClientDataSet PacketRecords Property Not Equal To -1 Causes Blank Records To Be Displayed | No |
| 1 | 1535 | Kylix and Delphi Source Code Does Not Match the Compiled DCUs That Ship with DBISAM | No |
| 1 | 1536 | Certain Live SELECT Queries and Filters Cause #8965 "Page Buffers Corrupt" Errors | Yes |
| 1 | 1539 | Single-Row SELECT COUNT(*) Statement Returns the Incorrect Count of the Total Records After Deletes | No |
| 1 | 1542 | TOP N SELECT Queries Improperly Returning Distinct Results | No |
| 1 | 1549 | Specifying Parameters on Left-Hand Side of Binary Operators Causes Type Mismatch in Filters and SQL | No |
| 1 | 1551 | Using a NOT Operator Around a Large Block of OR Expressions in Live Query Can Cause an AV | No |
| 1 | 1552 | Record Counts Greater Than Number of Records in Table When Certain Filters Applied to a Table | No |
| 1 | 1553 | Dropping the Primary Index in a Table Using the DROP INDEX SQL Statement Causes an AV | No |
| 1 | 1556 | SQL CREATE TABLE LAST AUTOINC Clause Not Parsing Correctly | No |
| 1 | 1557 | SQL CREATE TABLE Statement LOCALE CODE Clause Won't Accept 0 as a Valid Locale Code | No |
| 1 | 1558 | Executing a SQL DROP INDEX Statement with a Full Path Name in the Table Correlation Name Fails | Yes |
| 1 | 1559 | SQL RUNSUM Aggregate Function Returning the Same Result as the SUM Aggregate Function | No |
| 1 | 1562 | Posting of Updates Using ADO Express and ODBC Driver Failing | No |
| 1 | 1563 | Using LIKE Operator With a Constant Single Character and a Wildcard Causes Incorrect Results | Yes |
| 1 | 1564 | Using NULL String Constant Expressions in SQL SELECT Columns Causes Invalid Field Definition Error | Yes |
Minor Problems
| Build | # | Title | Workarounds |
| 1 | 1561 | Error In Manual Under Customizing the Engine Section for Custom Functions Example | 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 |
