Thanks Richard and Bruce,
are the values you are updating (and saving away) on the form itself?
or just other values in the record?
Are you aware that the "server side" code will run when the user clicks on "save"?
So your "updating code" will run here as well?
Personally I would not "interim" save the record before the user clicks on save, because it would make the "cancel" into a "sort-of" cancel.
So I think your root pattern is wrong anyway. Perhaps change your pattern so the correct values are set into the record, and session-values, but you don't actually save the record in the "server side code".
I am not convinced that the code is run twice - when I click the button and when the record is saved.
Because this is what I am doing in the event:
- Make a new workorder (child record of the record shown)
- Updating a date field on the record shown to the next date to be serviced.
And there is only one new child record created.
So what is NOT working is setting the date field on the shown record.
The code is this:
MCus:NaesteCheck = MSagH:Lev_Dato_start + int(MCus:Interval * 30.4166)
p_web.SSV('MCus:NaesteCheck ', MCus:NaesteCheck )
Access:MobCustomers.Update()
I would have thought that the p_web.SSV('') would update the screen value but it does not.
So I guess my real questions is: how can I update the screen value from an embed?
Or - as Richard suggests: how can I refresh the shown record with the disk values?
/Poul