Incident Reports Addressed in 1.05

Incident Reports Addressed in 1.05

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

Serious Problems

Build

#

Title

Workarounds

1	2416	Newly-Created Jobs Do Not Run on the ElevateDB Server	Yes
1	2417	ALTER TABLE ADD COLUMN AT With 0 As Position Causes Internal Column Usage Instead	Yes
1	2418	Clearing a CLOB Column in a Remote Session Can Cause the CLOB Column to be Filled with Garbage	No
1	2419	CHAR Columns Showing Garbage in Unicode Version	No
1	2423	Using NOT in a Filter Expression Can Cause AV	Yes
1	2424	Table Buffering Settings Not Being Permanently Saved to the Database Catalog	No
1	2426	GROUP BY Queries on More than 16 Columns Causes Incorrect Results	No
1	2427	Procedures That Return an Insensitive Result Set Can Cause an AV	No
2	2433	Calling FlushBuffers Method While in a Transaction Causes Premature Commit	Yes
2	2435	Un-Optimized Locate Returns True for Tables with Deleted Rows that Satisfy the Locate	No
2	2438	Unicode Errors Causing Format Error Instead of Displaying Error	No

Minor Problems

Build

#

Title

Workarounds

1	2421	WITH DATA and WITH NO DATA Clauses for CREATE TABLE AS Should Be Mandatory	Yes
1	2422	Specifying a MIGRATE DATABASE Parameter Incorrectly Can Cause AV	Yes
1	2425	Leading Spaces in Column Names Causes Locate to Raise Error Regarding Non-Existent Column	No
2	2434	EXPORT TABLE Statement With TIME FORMAT Clause and Without AM/PM Literal Clauses Causes AV	Yes
2	2436	Setting Previously-Assigned OnFilterRecord Event to Nil Can Cause Access Violation	No
2	2437	Long Database Names Cause Invalid Temporary Table Identifier Error with SQL Queries	Yes
2	2439	Using TABLE Clause Causes AV	No
2	2440	CDCollector Example Application Raises Error when Run	Yes

More Support Options

Search Incident Reports

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals