Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.filemaker > #1939

Re: Protect Container, best praxis

Show all headers | View raw

In article <fec4cea3-1b30-4a41-814d-5083774ad219@googlegroups.com>,
Jeremy Bante <jeremy.bante@gmail.com> wrote:
> On Thursday, December 11, 2014 8:07:57 AM UTC-8, Christoph Kaufmann wrote:
> >
> > Give the user a global Container field to play with?
> 
> Exactly. Make the actual data field non-enterable, and format the global
> container field to be invisible, then your OnObjectModify scripting can run
> the checks you want before (if choosing to accept the new file) copying the
> global field contents into the data field and clearing the global.

Or, depending on how the database is used, you could just disable user
access to the Container field and have an "Insert" button which runs a
script to do the necessary checks and import the object.

Helpful Harry  :o)

Back to comp.databases.filemaker | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Protect Container, best praxis clkaufmann@gmx.ch (Christoph Kaufmann) - 2014-12-11 17:07 +0100
  Re: Protect Container, best praxis Jeremy Bante <jeremy.bante@gmail.com> - 2014-12-11 13:59 -0800
    Re: Protect Container, best praxis Helpful Harry <HelpfulHarry@BusyWorking.com> - 2014-12-12 13:37 +1300
      Re: Protect Container, best praxis clkaufmann@gmx.ch (Christoph Kaufmann) - 2014-12-13 14:50 +0100
    Re: Protect Container, best praxis clkaufmann@gmx.ch (Christoph Kaufmann) - 2014-12-13 09:37 +0100

csiph-web