New Incident Reports for 2.00

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

Serious Problems

Build

Title

Workarounds

1	2647	Scrolling an SQL Script in the ElevateDB Manager that is Longer than 64k Lines Causes Error	No
1	2649	Creating a Temporary Table in a Procedure or Script Prevents Row Deletions Outside of Routine	No
1	2653	Joins that Have Multiple Dependencies Can Cause Incorrect Results	No
1	2654	CREATE STORE Causes AV for Remote Store	Yes
1	2659	Trying to Load an ElevateDB 1.x Stream Using 2.x Causes Error	No
1	2660	Altering a Constraint Causes a Parsing Error	No
1	2661	Altering a Table Immediately After Publishing a Table Causes Error	No
1	2662	Opening a Table Right After Restoring the Database Containing the Table Causes NULL ColumnValues	Yes
1	2663	ElevateDB Manager Issuing Error When Logging In as Non-Administrator	No
1	2665	Attempting to CAST an Empty String to a FLOAT Value Causes an Access Violation	Yes
1	2666	SUBSTR Function Not Handling Non-Constant Parameters for the Second Parameter Properly	No
1	2668	SAVE UPDATES Statement Not Clearing Published Updates from Published Tables	No
1	2669	Passing Empty String Parameters to TRIM, LTRIM, and RTRIM Causes an AV	No
2	2675	Long Index Names Cause Error During Migration from DBISAM Tables	Yes
2	2676	Deleting the Contents of a TDBMemo Control Sets the Underlying Column to NULL	No
2	2677	Having Many Deleted Rows in a Table Can Negatively Affect INSERT, UPDATE, or DELETE Performance	No
2	2679	LOAD UPDATES Failing When Replication Data Has Passed Through More than One Publisher	No
2	2680	Using a Boolean Column by Itself in a WHERE Clause Expression Causes All Rows to be Selected	Yes
2	2681	Inserting Rows into a Table with Very Large Index Keys Can Cause Hang	No
2	2682	Truncation of String Values Not Raising an Exception	No
2	2687	Engine Accumulating Memory During Session Opens	No
2	2688	Using Specific DatabaseName in UPDATE or DELETE Statement Can Cause Subsequent Catalog Read Error	No
2	2689	ODBC Driver Causing Commit Error with Microsoft Access	No
2	2690	ODBC Driver Causing ODBC Call Failed Error When Opening Table in Access with TimeStamp Column	No
2	2691	ODBC Driver Causing Rouding Error When Opening Table in Access with Decimal Column	No
2	2693	ElevateDB .NET Data Provider Does Not Remove Temporary Tables	No
2	2694	Trying to Connect an ElevateDB 2.x Application to an ElevateDB 1.x Server Fails	No
2	2697	LOAD UPDATES Can Fail with a Row Changed Error if Row Change Detection Turned On	No
2	2698	External Function with VARCHAR Return Data Type Can Cause Truncation Error	No

Minor Problems

Build

Title

Workarounds

1	2646	Altering a View and Cancelling Causes ElevateDB Manager to Prompt User	No
1	2648	Changing Result Set Columns for Scripts or Statements Causes Incorrect Result Grid Column Display	Yes
1	2650	Font Size Setting for SQL Editor Not Being Saved Properly in the ElevateDB Manager	No
1	2651	ElevateDB VCL Manuals Contain Incorrect Path Information for Recompiling Source Code Topic	No
1	2652	WinHelp SQL Manuals Contain Truncated Text	No
1	2656	EXPORT TABLE Example in SQL Manual Refers to IMPORT TABLE Statement	No
1	2657	Altering a Trigger in a Way that Causes a Non-SQL Error Causes "Unable to Focus" Error	No
1	2664	Activating Engine without ConfigPath Property Set Causes IDE to Crash or Display Errors	Yes
1	2667	Target Table Constraints Not Displaying Properly without Selecting Target Table in ElevateDB Manager	Yes
2	2674	Multiple Values Are Allowed for Scalar Sub-Queries	No
2	2678	Defining Computed Columns Too Small for the Data Results in Value Truncation Error	Yes
2	2685	Double-Clicking on a Table in the EDB Manager to Open the Table Can Cause an AV	No
2	2686	Attempting to Open a Connection When the Configuration Path Contains Invalid EDB DLL Can Cause Error	No
2	2692	ElevateDB Error Messages Appendix Still Contains Some Links to ElevateDB 1 SQL Manual	No
2	2695	Migrating a DBISAM Database Containg Indexes with the Prefix "Text_" in the Name Causes Error	Yes
2	2696	Filter Not Being Updated When Table Is Re-Opened in the ElevateDB Manager	No

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap