Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Incident Reports » Incident Reports Addressed in 1.16 |
Build | # | Title | Workarounds |
1 | 437 | Auto-Increment Fields Randomly Increment by More Than One During Appends | Yes |
1 | 439 | Restructure Process Is Not Saving the Data File Header Information Correctly | No |
1 | 441 | Need to Make WITH LOCKS SQL Clause Use Read Locks Instead of Write Locks | Yes |
1 | 444 | Problem with Re-Positioning On Current Record After Modifications with Un-Optimized Filter Set | No |
1 | 445 | Error Occurs When Deleting a Any Secondary Index Except for the Last Available | No |
1 | 446 | A Key Not Found Error is Triggered During Many Random Operations On Table Opened Exclusively | No |
1 | 448 | Using Locate Method on an In-Memory TDBISAMTable Component Causes Error | No |
1 | 450 | Using Rollback Method For Active Transaction Does Not Automatically Cancel Pending Edit | Yes |
1 | 455 | Locate Not Working Correctly With Non-ASCII Language Driver and Compound Indexes | No |
1 | 458 | Using Any Characters Above Chr(128) As First Character of Field Names Not Permitted | No |
1 | 459 | Problems When Using Field Names As Constants in SQL Queries | Yes |
1 | 460 | Optimized Filters On NULL Values Not Working Properly | No |
1 | 462 | Using INTO Clause With SQL Queries Results in Table in Wrong Primary Index Order | Yes |
1 | 463 | Import Functionality in Database System Utility Not Handling Embedded Commas Properly | No |
This web page was last updated on Wednesday, October 30, 2024 at 11:41 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |