Database Reference
In-Depth Information
set the script to run with full access privileges, then you can even delegate password resetting
to someone else. The Reset Account Password step needs an account name and a new pass-
word to do its job.
Change Password
You'll probably use this script step only in cases where you're creating a special layout that
lets people who don't have full access privileges manage security. For example, you may
have someone on staff who should be able to manage accounts, but you don't want him to
have full access privileges. So you can build a special layout (or two), and write scripts that
run with full access privileges to manage all your security tasks. That way, you can even do
special workarounds like allowing some members of a privilege set to change their pass-
words without giving this power to each of them. To do so, you usually need a user's table
with a field that controls who can and can't run your Change Password script.
Enable Account
Once you've created a bunch of new accounts using the Add Account step, the Enable Ac-
count step lets you turn them on and off at will. That way, you can create accounts for, say,
an entire class of students, and later turn on accounts for those who've arrived on campus.
This step sets the appropriate Account Status, and it works only when there's a valid account
name that matches your script settings.
Re-Login
The most exciting step in the Accounts section is Re-Login. It provides a function that
doesn't exist anywhere else in FileMaker. It lets you switch to a different account without
closing the file, which makes testing security settings a lot more convenient. Instead of open-
ing and closing the files until your mouse button wears out, just run a Re-Login script. Add
steps in the script that set global fields on pertinent layouts to
Get(AccountName)
and
Get(AccountPrivilegeSetName)
so you can keep track of what you're testing as you re-lo-
gin over and over. To get the most realistic testing conditions, make sure your Re-Login
script calls any script that runs when your file opens.
You can also use Re-Login when someone inevitably calls you to his desk to show you a
problem in the database. Just re-login as an account with full access and then you can poke
around and find out what's happening
on his computer
. When you re-login, you're not just
saving time by not closing and reopening the file: You can actually work in the same win-
dow, on the same record, with the same found set and sort order without all the trouble of re-
creating the situation back at your desk.
