hi,
if I add the function sc_redir at event onafterupdateall or onafterupdate
the form application does not update anything field but just makes the redir
hi,
if I add the function sc_redir at event onafterupdateall or onafterupdate
the form application does not update anything field but just makes the redir
Re: UPDATE BUTTON AND SC_REDIR
Not sure how you created your apps, but by putting the Sc_redir function in the event as mentioned, and it did redir than it is functioning as intended.
That event is executed after update is perform. So if you form did not update, then somewhere else is having a problem.
Re: UPDATE BUTTON AND SC_REDIR
test and see.
if I remove the redir the application work perfectly
Re: UPDATE BUTTON AND SC_REDIR
Hello,
I have reported this issue to our bugs team for further testing. What kind of form are you working with? Is this a editable grid form?
regards,
Bernhard Bernsmann
Re: UPDATE BUTTON AND SC_REDIR
no is a sigle record form
Re: UPDATE BUTTON AND SC_REDIR
is on every form type. is a big big problem!!!
Re: UPDATE BUTTON AND SC_REDIR
Hi,
I ran into the same bug and I needed an immediate solution.
Here is the workaround I use till it’s fixed.
I perform a simple sc_lookup() on the primary key of the record I just updated. If it’s OK, redirect to the grid.
Hope this helps.
jsb
Hello,
This problem still persists?
Yes the problem still persist
Yes, I have the same problem.
Here’s a workaround:
It depends on your situation, but fire a sc_commit_trans() should do it.
I think what’s happening is because of the redirect it doesn’t reach the actual commit
and therefor the transaction never gets completed.
jsb
Works!
Thank you jsb!
This is not a bug and it’s been discussed in this forum several times. You need to use the commit if you want to do a sc_redir.
from the documentation (the helpfile)
If the user, in any of these events, use an application redirectioning (macro “sc_redir”) must before the redirect, use this macro to guarantee the transactions previously effected.
100% true. Mea culpa.