Icon View Incident Report

Minor Minor
Reported By: Joachim Mainusch
Reported On: 1/21/2014
For: Version 2.15 Build 3
# 3999 ReadOnly Property of TEDBTable, TEDBQuery, TEDBScript, and TEDBStoredProc Being Cached

To reproduce the problem:

Step 1)
Run the Stored Procedure "GetAllVgArtikel" as it is, with no modifications. Enter "100" as input parameter. The result is a recordset with 2 records. The recordset is editable. Everything OK.

Step 2)
Modify the Stored Procedure "GetAllVgArtikel": add the column "dVORGAENGEuARTIKEL.VgNummerSource" (or any other column) to the "ORDER BY" clause. Run the procedure. Enter "100" as input parameter. The result is a recordset with 2 records. The recordset is now READONLY, and remains READONLY, even if the ORDER BY clause is re-set to the original value, or even if no ORDER BY is entered at all.


Comments Comments
ElevateDB now properly separates the "request read-only" behavior from the "dataset is read-only" behavior in the datasets. Also, the ReadOnly property was moved from the descendant classes into the ancestor TEDBDataSet class.


Resolution Resolution
Fixed Problem on 1/23/2014 in version 2.16 build 1


Products Affected Products Affected
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

Image