WinXP, EWB 2.02 B2 & 3, DBISAM C/S Ver 4.26 Build 2.

Chrome test browsers on both current and separate computers.

I am using a dataset's BeforeUpdate and AfterSave events to respectively start and commit a transaction for each record that is updated by the User.

This works fine with Build 1 but fails with Builds 2 & 3 with the following error:

Uncaught Error: Database commit response error(Error)
Line: 1

The commit "Payload" in the browser reports null values in the beforerow and incomplete afterrow values:

{   "operations": [ { "dataset": "WorkOrderTasks", "operation": 2, "beforerow": { "WorkOrderID": null, "TaskOrder": null, "TaskID": null, "TaskTitle": null, "TaskDetail": null, "TaskOutcome": null, "ExpectedOutcome": null, "Comments": null, "TaskDocumentFile": null }, "afterrow": { "Comments": "" } } ] }

Re-installing Build 1 and all appears to work correctly again.

Additional Notes:

With Build 1, I use a manually updated version of the weblists unit which includes Tim's Hot update.

When updating to a different build in either direction, I have to delete the dataset on the form and drag it back from the Dataset Manager to get things to work again. Failing to do this has resulted in unstable IDE behaviour with AV's even when selecting Project>>Options.

Attached is a sample app assembled with B1 and including SQL to generate the associated table.
Roland

Ok. So it isn't me. I spent all night wondering why a simple Commit was not working.

I am using ElevateDB.

The error message I get is:

'Database commit response error ('null' is not a valid integer value for field 'fldName')
'Line: 19314'

FYI, the error does NOT occur for a StartTransaction...Insert...Commit.

It occurs for a StartTransaction...Update...Commit.

And, I am using the built-in browser window.

Same problem.  App working correct in EWB 2.02 B1 now generating error with B2 & B3

Paul

On 10/25/2015 8:06 PM, Roland wrote:
> This works fine with Build 1 but fails with Builds 2 & 3 with the following error:
> Uncaught Error: Database commit response error(Error)
> Line: 1
> The commit "Payload" in the browser reports null values in the beforerow and incomplete afterrow values:
> {   "operations": [ { "dataset": "WorkOrderTasks", "operation": 2, "beforerow": { "WorkOrderID": null, "TaskOrder": null, "TaskID": null, "TaskTitle": null, "TaskDetail": null, "TaskOutcome": null, "ExpectedOutcome": null, "Comments": null, "TaskDocumentFile": null }, "afterrow": { "Comments": "" } } ] }


Seeing this on Update and Delete operations on dataset.

Insert is OK.

The issue is with null values here as well.


> Re-installing Build 1 and all appears to work correctly again.

Looks OK here as well.

Did quick diff between b1 and b3 framework and nothing obvious jumoped
out so need Tim to track this one down (most of the data changes appear
to be around readonly and change tracking).

Raul

Roland,

<< This works fine with Build 1 but fails with Builds 2 & 3 with the following error: >>

This is now fixed.  I'm doing a new build today that will fix it.

<< When updating to a different build in either direction, I have to delete the dataset on the form and drag it back from the Dataset Manager to get things to work again. Failing to do this has resulted in unstable IDE behaviour with AV's even when selecting Project>>Options. >>

I'm not seeing anything like that here.  Are you doing anything with the dataset at all (modifications, etc.), other than updating the build of the IDE ?

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

Roland,

<< This works fine with Build 1 but fails with Builds 2 & 3 with the following error: >>

This is now fixed.  I'm doing a new build today that will fix it.

<< When updating to a different build in either direction, I have to delete the dataset on the form and drag it back from the Dataset Manager to get things to work again. Failing to do this has resulted in unstable IDE behaviour with AV's even when selecting Project>>Options. >>

I'm not seeing anything like that here.  Are you doing anything with the dataset at all (modifications, etc.), other than updating the build of the IDE ?

Tim

No - simply doing the installs and opening the IDE which of course loads the application by default. I even had repetitive AV's when trying to delete the dataset which required a forced shut down using the task manager. After reopening the IDE - I was able to delete and replace the dataset without problems.

Am I right in assuming the use of Win XP is OK and that the only problem is the Internet Explorer version limitation?

Roland.

Roland,

<< Am I right in assuming the use of Win XP is OK and that the only problem is the Internet Explorer version limitation? >>

Well, officially we're Vista and higher and don't test with XP, so I really can't give you a definite answer.  *On paper*, yes, the IDE should work fine under XP.  But, the IDE is created using Delphi XE6, and as far as I know, they've discontinued supporting XP with the later versions of Delphi and there could be something in the RTL that is having an issue, also.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

Roland,

<< Am I right in assuming the use of Win XP is OK and that the only problem is the Internet Explorer version limitation? >>

Well, officially we're Vista and higher and don't test with XP, so I really can't give you a definite answer.  *On paper*, yes, the IDE should work fine under XP.  But, the IDE is created using Delphi XE6, and as far as I know, they've discontinued supporting XP with the later versions of Delphi and there could be something in the RTL that is having an issue, also.

Tim Young
Elevate Software
www.elevatesoft.com

Tim

Thanks for that. Having reverted back to Build 1, I have tried a couple of other example applications for IDE instability and they appear OK.

It appears that my main application must now have a problem as I get the following error when selecting Project>>Options:

(GDI+Error) One of the arguments passed to the method was not valid.

This is what started the continuous Av's requiring a forced shut down described before. Other than this - the application behaves as expected under the IDE and at runtime.

Roland