Abandon changes on request find: Difference between revisions
From DataFlex Wiki
Jump to navigationJump to search
Created page with "I recently had a customer complain that closing a view will trigger "Abandon Changes?" - but using Find Next/Previous does not. Once I thought about it, I realized this really wa..." |
Hsymington (talk | contribs) m Added to Tutorials category |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 8: | Line 8: | ||
If (iAnswer<>MBR_Yes) Procedure_Return | If (iAnswer<>MBR_Yes) Procedure_Return | ||
End | End | ||
Forward Send Request_Find mode entUpdtFlag | Forward Send Request_Find mode entUpdtFlag | ||
End_Procedure | End_Procedure | ||
| Line 15: | Line 15: | ||
taken from: | taken from: | ||
https://support.dataaccess.com/Forums/showthread.php?60389-Abandon-Changes-when-finding | https://support.dataaccess.com/Forums/showthread.php?60389-Abandon-Changes-when-finding | ||
[[Category:How To]] | |||
[[Category:Tutorials]] | |||
Latest revision as of 11:42, 25 March 2020
I recently had a customer complain that closing a view will trigger "Abandon Changes?" - but using Find Next/Previous does not. Once I thought about it, I realized this really wasn't just another "OK, they're the customer..." request.
Procedure Request_Find Integer mode Integer entUpdtFlag
Integer iAnswer
If ((HasRecord(Server(Self))) and (Should_Save(Server(Self)))) Begin
Move (YesNo_Box("Changes Exist. Abandon changes and continue with the find?", "Confirm")) to iAnswer
If (iAnswer<>MBR_Yes) Procedure_Return
End
Forward Send Request_Find mode entUpdtFlag
End_Procedure
taken from:
https://support.dataaccess.com/Forums/showthread.php?60389-Abandon-Changes-when-finding
