New Incident Reports for 2.17

New Incident Reports for 2.17

The following is a list of the new incidents reported for version 2.17. Click on the incident # in order to view the details of the incident report.

Serious Problems

Build

#

Title

Workarounds

1	4050	Step Over Functionality Not Working in ElevateDB Manager Script Debugger	No
1	4064	COUNT * Not Working Properly when WHERE Clause Contains Correlated Sub-Query	No
1	4073	Reverse-Engineering Functionality Not Using Correct Dependency Order for Triggers	No
1	4082	Configuration Log Events Can Become Stuck and Stop Reflecting New Events after Refresh	No
1	4086	IMPORT TABLE Statement Can Experience AV with QUOTE CHAR of #0 (Null)	Yes
1	4105	Join Optimizer Not Selecting Optimal Join Orders Based Upon Available Indexes	No
1	4106	Changing a Column Name Included in a Foreign Key in the Alter Table Dialog Can Cause AV	No
1	4107	Freeing a Query with Manually-Locked Rows Can Result in Dangling Row Locks	Yes
1	4108	Attempting to Rename a Database to an Existing Database Corrupts Configuration	No
1	4145	Cannot Use the CAST() Function to Convert a String into a BLOB Value for Insertion	No

Minor Problems

Build

#

Title

Workarounds

1	4058	Reverse-Engineered SQL for Stores Not Correct	No
1	4074	Saved Invalid Filter Expressions in ElevateDB Manager Preventing Proper Table Opens	No
1	4078	Character Set Setting Not Being Save Properly for ODBC DSNs	No
1	4100	Changing the Node Display Type in the ElevateDB Manager Explorer Can Cause Access Violation	No
1	4102	64-bit Issues with ElevateDB Manager Source Code	No
1	4103	COUNT Function Not Working Properly with Non-Table Queries	No
1	4104	Invalid Date Values Allowed into Stored Procedure Parameters	No
1	4109	Cannot Access NEWROW Columns from FETCH Statement in BEFORE INSERT Triggers	No

More Support Options

Search Incident Reports

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals