Icon 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

12647Scrolling an SQL Script in the ElevateDB Manager that is Longer than 64k Lines Causes ErrorNo
12649Creating a Temporary Table in a Procedure or Script Prevents Row Deletions Outside of RoutineNo
12653Joins that Have Multiple Dependencies Can Cause Incorrect ResultsNo
12654CREATE STORE Causes AV for Remote StoreYes
12659Trying to Load an ElevateDB 1.x Stream Using 2.x Causes ErrorNo
12660Altering a Constraint Causes a Parsing ErrorNo
12661Altering a Table Immediately After Publishing a Table Causes ErrorNo
12662Opening a Table Right After Restoring the Database Containing the Table Causes NULL ColumnValuesYes
12663ElevateDB Manager Issuing Error When Logging In as Non-AdministratorNo
12665Attempting to CAST an Empty String to a FLOAT Value Causes an Access ViolationYes
12666SUBSTR Function Not Handling Non-Constant Parameters for the Second Parameter ProperlyNo
12668SAVE UPDATES Statement Not Clearing Published Updates from Published TablesNo
12669Passing Empty String Parameters to TRIM, LTRIM, and RTRIM Causes an AVNo
22675Long Index Names Cause Error During Migration from DBISAM TablesYes
22676Deleting the Contents of a TDBMemo Control Sets the Underlying Column to NULLNo
22677Having Many Deleted Rows in a Table Can Negatively Affect INSERT, UPDATE, or DELETE PerformanceNo
22679LOAD UPDATES Failing When Replication Data Has Passed Through More than One PublisherNo
22680Using a Boolean Column by Itself in a WHERE Clause Expression Causes All Rows to be SelectedYes
22681Inserting Rows into a Table with Very Large Index Keys Can Cause HangNo
22682Truncation of String Values Not Raising an ExceptionNo
22687Engine Accumulating Memory During Session OpensNo
22688Using Specific DatabaseName in UPDATE or DELETE Statement Can Cause Subsequent Catalog Read ErrorNo
22689ODBC Driver Causing Commit Error with Microsoft AccessNo
22690ODBC Driver Causing ODBC Call Failed Error When Opening Table in Access with TimeStamp ColumnNo
22691ODBC Driver Causing Rouding Error When Opening Table in Access with Decimal ColumnNo
22693ElevateDB .NET Data Provider Does Not Remove Temporary TablesNo
22694Trying to Connect an ElevateDB 2.x Application to an ElevateDB 1.x Server FailsNo
22697LOAD UPDATES Can Fail with a Row Changed Error if Row Change Detection Turned OnNo
22698External Function with VARCHAR Return Data Type Can Cause Truncation ErrorNo

Minor Problems

12646Altering a View and Cancelling Causes ElevateDB Manager to Prompt UserNo
12648Changing Result Set Columns for Scripts or Statements Causes Incorrect Result Grid Column DisplayYes
12650Font Size Setting for SQL Editor Not Being Saved Properly in the ElevateDB ManagerNo
12651ElevateDB VCL Manuals Contain Incorrect Path Information for Recompiling Source Code TopicNo
12652WinHelp SQL Manuals Contain Truncated TextNo
12656EXPORT TABLE Example in SQL Manual Refers to IMPORT TABLE StatementNo
12657Altering a Trigger in a Way that Causes a Non-SQL Error Causes "Unable to Focus" ErrorNo
12664Activating Engine without ConfigPath Property Set Causes IDE to Crash or Display ErrorsYes
12667Target Table Constraints Not Displaying Properly without Selecting Target Table in ElevateDB ManagerYes
22674Multiple Values Are Allowed for Scalar Sub-QueriesNo
22678Defining Computed Columns Too Small for the Data Results in Value Truncation ErrorYes
22685Double-Clicking on a Table in the EDB Manager to Open the Table Can Cause an AVNo
22686Attempting to Open a Connection When the Configuration Path Contains Invalid EDB DLL Can Cause ErrorNo
22692ElevateDB Error Messages Appendix Still Contains Some Links to ElevateDB 1 SQL ManualNo
22695Migrating a DBISAM Database Containg Indexes with the Prefix "Text_" in the Name Causes ErrorYes
22696Filter Not Being Updated When Table Is Re-Opened in the ElevateDB ManagerNo