FMPRO-L Archives

April 2011, Week 4

FMPRO-L@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Corn Walker <[log in to unmask]>
Reply To:
FileMaker Pro Discussions <[log in to unmask]>
Date:
Thu, 28 Apr 2011 06:52:14 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (16 lines)
On Apr 27, 2011, at 11:36 PM, Richard S. Russell wrote:

> I was musing in the car on the drive home tonight that one approach to databases is to have the data stored in one file and the user interface in another. This got me to speculating on the prospects of having a multi-file system where all of the SCRIPTS are in a file of their own. Has anybody ever tried this? How did it work out?

It doesn't work out very well. Scripts execute based on the context of the file they are in, so unless they're all in your UI file, having them elsewhere is a non-starter.

Separating the data and the interface into separate files does work out, and it's something people do all the time. Placing all of the scripts into your UI file will work with some caveats, the primary one being that security is defined at the file where the data is defined. So if you want to prevent a user from deleting records except with your script, and you use the security restrictions to do this, you'll need a script in the data file to override those security restrictions.

Cheers,
-corn


Cornelius Walker
The Proof Group
http://proofgroup.com/

ATOM RSS1 RSS2