This topic is locked
[SOLVED]

 Error Occurred on inline edit when update=false

2/16/2012 3:01:47 PM
ASPRunnerPro General questions
T
Tim author

Hello,
version 7.0 build 10638 (and previous). When I set BeforeEdit=false in the "Before record updated" event and then attempt an inline edit, the page shows "Error occurred", which is a link but there is no further info. If I have other code in that event the code runs fine, but the error is shown (the error is also shown if there is no extra code). So everthing appears to be ok, but the error is thrown on the page.
I've tried this on a couple of different projects as a test. It seems if the list page is part of a master/detail relationship (either master or detail), or if the list page is made up of a query that joins another table, then this inline edit error messages happens. If the list page is just one table the error doesn't show.
Thanks,

Tim

Sergey Kornilov admin 2/16/2012

Tim,
I'm not quite sure I understand what is your question. Please elaborate.

T
Tim author 2/16/2012

Thanks for the quick reply. I'd say it appears to be a bug. To recreate:
> create a list page with a query that contains a "join", or create a master/detail relationship on the tables page of the wizard,

> then set BeforeEdit=false in the "Edit Page/Before record updated" event for that table,

> then after publishing the app, attempt to save an inline edit

> this will produce an "Error occurred" message on that row.
Let me know if you need more info.

Thanks,

Tim

Sergey Kornilov admin 2/16/2012

This is not a bug.
If you prevent record from being edited you have to tell user what happened. In inline edit mode the only way to do so is to utilize "Error occurred" popup. Assign value to message variable to tell user what happened:

message = "something happened"

BeforeEdit=false
T
Tim author 2/17/2012

Ah, thanks. If I put anything in the message it keeps the "Error occurred" message from showing, as you say (the message I put in doesn't show either - at least when doing an inline edit - but that doesn't matter).
I figured "bug" wasn't correct but I didn't have any better way to describe what I was seeing.
Thanks for the help, as always!

Tim