Incident Reports Addressed in 2.24

Incident Reports Addressed in 2.24

The following is a list of the incident reports addressed in version 2.24. Click on the incident # in order to view the details of the incident report.

Serious Problems

Build

#

Title

Workarounds

1	4374	Locate on Non-Active Index Can Cause #601 Error When Used Right After Failed FindKey	No
1	4380	CASTing a BLOB as a VARCHAR Causes Conversion Error	No
2	4384	Heavy Load on ElevateDB Server Can Cause Excessive Thread Creation	No
3	4419	ElevateDB Server Can Experience a #505 Error Message During Shutdown	No
3	4420	Using ANSI External Modules with Unicode-Compiled Application Results in Missing Error Mesages	No
3	4421	Using IFNULL Functions with a Parameter in the First Argument Can Result in Error #1011	No
3	4422	Trying to Modify a Column Involved in a Computed BLOB Column Causes "Field Cannot Be Modified" Error	No
3	4423	ElevateDB Manager Not Showing a Progress Bar Correctly When Running on Windows 10	No
3	4424	Using aParameter in an IFNULL Function in the WHERE Clause Can Cause Incorrect SELECT Query Results	No
3	4425	Migrating a Database from ElevateDB ANSI to Unicode Results in a Collation Error	No
3	4427	REVOKE ALL Statement Does Not Work on Database Objects Like Tables and Views	Yes
3	4428	The ElevateDB Server Can Experience an AV in the Server UI Under Heavy Load	No
3	4429	TEDBSession Component Can Experience an AV During Destruction via Component Removal Notifications	No

Minor Problems

Build

#

Title

Workarounds

1	4381	Next Run Date/Time for Jobs Being Calculated Incorrectly	No
2	4382	Reverse Engineering and COMPARE DATABASE Statement Not Generating Code for View Indexes	No
2	4383	DBISAM 4 Migrator Using Trial Version of DBISAM Database Engine	No

More Support Options

Search Incident Reports

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals