 |  LoginProducts  SalesSupportDownloadsAbout |
| Home » Technical Support » DBISAM Technical Support » Incident Reports » Incident Reports Addressed in 2.07 |
Incident Reports Addressed in 2.07The following is a list of the incident reports addressed in version 2.07. Click on the incident # in order to view the details of the incident report.
Serious Problems
Minor Problems
Serious Problems
| Build | # | Title | Workarounds |
| 1 | 706 | DBSYS SQL-92 Reverse Engineering Not Working Properly for Tables Without a Primary Index | No |
| 1 | 707 | Including a BLOB Column in a SQL SELECT Query with a GROUP BY Clause Causes #8708 Error | No |
| 1 | 708 | Queries and Filters on Tables Using a Non-English or ANSI Language Driver Return Incorrect Results | No |
| 1 | 710 | UpgradeTable Method Failing with Access Denied Error Message When Table Should Be Closed | No |
| 1 | 711 | Using NOAUTOINC with an SQL INSERT Statement That Uses a SELECT Statement Does Nothing | No |
| 1 | 712 | Using Suppression of AutoInc Values and Editing AutoInc Values Causes Error on Delete of Same Record | No |
| 1 | 714 | DELETE and INSERT SQL Statements Causing Error with COMMIT INTERVAL Clause | No |
| 1 | 715 | RowsAffected Property Incorrect For INSERT, UPDATE, or DELETE Queries that are Implictly Rolled Back | No |
| 1 | 716 | Using Locate Method on Query Result Sets Returns Random Results | No |
| 1 | 717 | Compiling an Application with Range Checking Turned On Causes Range Errors When Table Opens Fail | No |
| 1 | 718 | Using Non-Join Expressions in SQL JOIN Conditions Causes Incorrect Results | No |
| 1 | 719 | Locate Method of TDBISAMTable Not Working Properly After Record is Just Added | No |
| 1 | 720 | Min/Max/Default Validity Checks for SmallInt Fields Not Being Transferred Properly | No |
| 1 | 721 | Using Locate to Do a Partial-Key Search on The Active Index When No Records Exists Causes Error | No |
| 1 | 725 | Using CopyOnAppend Property Can Cause BLOB Corruption After Append | No |
| 1 | 727 | DBSYS Reverse-Engineering Process Always Sets Last AutoInc Value Even if Not Adding Existing Data | Yes |
| 1 | 728 | Using a Column Name in SQL HAVING Clause When Column Is Aliased Causes AV | Yes |
Minor Problems
| Build | # | Title | Workarounds |
| None |
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 |
