Issue 118978 - Ask before saving (committing) changed records
Summary: Ask before saving (committing) changed records
Status: UNCONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: recent-trunk
Hardware: PC Windows XP
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-26 23:02 UTC by mike.hartley46
Modified: 2013-06-03 04:26 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description mike.hartley46 2012-02-26 23:02:20 UTC 
Why is this suicidal practice still possible (in v3.3.0) (at least in Windoze) in both forms and naked tables

It should surely be impossible (by default) to jump records without first demanding save current record edits? [yes|no]. Worse, if the most recent record visited is not edited then even though possibly every other record of the session was tampered with, all edits are committed but the form window is closed without question.
Comment 1 Rainer Bielefeld 2013-06-03 04:26:57 UTC 
As far as I know the current behavior is intended and can't be changed easily. But of course, most people would be happy th have a mode what allows to leave a record or the document without applying latest changes. So Enhancement.