View Incident Report

Serious

Reported By: Geroglidis Giannis
Reported On: 5/10/2011
For: Version 2.05 Build 7

# 3443 Updates to a Table Can Cause Next/Prior Operations on a Table Cursor to Skip Rows

When we scroll an EDBTable (for example when a report is printed for a specific month) and at the same time, other users on the same table are inserting records (in this case not in this month -- this means out of the scrolling range) this has as a result the scrolling on the EDBTable to be abnormal. The result is that some records are skipped and the report has different results on each execution.

Comments

The problem was that the change detection for the table cursors was refreshing and then executing another navigation operation (next/prior), so that the end result would be that a row was skipped. This applies only to end-user table cursors that navigate using an active index, and does not apply to the navigation performed internally by SQL operations for selecting rows, etc.

Resolution

Fixed Problem on 5/11/2011 in version 2.05 build 8

Products Affected

ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB PHP Standard
ElevateDB PHP Standard with Source
ElevateDB PHP Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap