Developer’s Guide

Using the Developer Utilities 27
4. Add a button to activate the script.
5. Repeat steps 3 and 4 for each upgraded file.
6. Use the Developer Utilities to bind your upgraded solution files
into the new runtime database solution.
7. Test your buttons in the runtime application.
Use sample data to make sure the records import properly and data
is imported to the correct fields.
8. Distribute the new solution files that contain the buttons.
9. Provide instructions telling users how to import data into the new
solution files.
Users can copy their old files into the “Old Solution Files” folder and
use the buttons in the new files to convert the old files and import
records from them into the new solution files.
Removing full access privileges
from databases
FileMaker Pro and FileMaker Developer use accounts, privilege
sets, and extended privileges to protect FileMaker databases. For
more information, see Help. You can use the Developer Utilities to
remove all administrative accounts from a file. For more information
about accounts and privileges, see Help.
Use the Developer Utilities to prevent users from altering the design
and structure of your database files and from changing any accounts
or privileges that you’ve set up. The
Remove admin access from files
permanently
option deletes from the database all accounts that were
using the Full Access privilege set. All Define dialog boxes will also
be unavailable, except for the Extended Privileges tab of the
Accounts & Privileges dialog box.
Note All database files must have at least one active account or they
can’t be opened. You can’t use the
Remove admin access from files
permanently
option if the accounts with Full Access privilege sets are
the only active accounts in the file. If you attempt to do so, you will
receive an error message.
Important Selecting this option permanently deletes from the
database all accounts that were using the Full Access privilege set.
This will permanently eliminate access to Layout mode and
ScriptMaker, and all Define dialog boxes, except for the Extended
Privileges tab of the Accounts & Privileges dialog box, for all
database files in the solution, whether they’re opened in a runtime
application, in FileMaker
Pro, or in FileMaker Developer. Structural
and design elements of the files cannot be modified by anyone,
including FileMaker employees. The only way to modify the tables,
field definitions, relationships, scripts, or access privileges is by
returning to the original file before it was customized by the
Developer Utilities.
Consider the long-term needs of your users when defining access
privileges. Communicate their access privileges to them clearly in
the About layout and follow the rules specified by FileMaker. For
more information, see
“Adding custom scripts to the About menu
command” on page 43.