Issue 62751 - Option to allow update of tables/views that don't have a 'bookmark' field
Summary: Option to allow update of tables/views that don't have a 'bookmark' field
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2006-03-03 14:42 UTC by rosspjohnson
Modified: 2013-02-07 22:38 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description rosspjohnson 2006-03-03 14:42:46 UTC
Base and Forms are too conservative in protecting against unintentional updates
to tables or views where Base is not provided with a recognisable 'bookmark' field.

This is a request to make this protection optional, leaving the current
protection as default, but to provide a switch, or switches, so that more
experienced designers can make use of the mechanisms at the DBMS level to ensure
updates operate correctly.

This option might be made available on a per form or subform basis.
Alternatively or inclusively, it might be an option at the data source
definition level (if that is feasible). The later makes sense as it explicitly
ties the chosen behaviour to a specific DBMS generally. The potential difficulty
with this is that one could change the option within the data source and all
applications that use it could inherit the changed behaviour.

A very useful solution could be achieved if it was a requirement to set an
option at BOTH the data source AND the form level. Thus an administrator might
have control over the data source definition option, and thus whether any
applications can turn this protection off, while general users would have
control over the per form option.
Comment 1 marc.neumann 2006-03-06 08:29:03 UTC

I reassign this enhancement to the User Experience team for evaluating.

Bye Marc