Development Guide
Table Of Contents
- Chapter 1 Setting up databases for FileMaker Go
- Chapter 2 Differences between FileMaker Go and FileMaker Pro
- Chapter 3 Designing databases for FileMaker Go
- Chapter 4 Protecting databases in FileMaker Go
Chapter 4 | Protecting databases in FileMaker Go 22
Notes
1 Filenames are case-sensitive. Script names are not case-sensitive.
1 The filename extension .fmp12 is not required.
1 You can define multiple variables in the same FMP protocol.
1 If spaces are needed in a link, replace every space with %20.
You can specify the account and password in the address (except when you’re opening hibernated
files).
Suggestions for protecting remote and local files
If your files need less security
1 Set a long server idle time for files served by FileMaker Server.
1 Increase the number of minutes before requiring re-login using the fmreauthenticate extended
privilege.
1 Don’t use the fmreauthenticate extended privilege.
If your files need more security — one user per device
Remote files
Try to balance security needs and user convenience when specifying the amount of time:
1 before the passcode is required
1 for server idle time
1 before requiring re-login using the fmreauthenticate extended privilege
Local files
1 Take additional precautions to prevent someone from accessing files on lost or stolen devices.
1 Use the fmreauthenticate extended privilege to minimize unauthorized access.
If your files need more security — multiple users per device
1 Set the passcode to be required immediately.
1 Set the fmreauthenticate extended privilege to fmreauthenticate0.
1 Users should be required to enter the passcode, then log in to files using their own accounts.