Instant Web Publishing Guide

32 FileMaker Instant Web Publishing Guide
For a list of error codes and descriptions, see the topic “Get(Last Error) function” in FileMaker Pro
Help.
If you don't want to create log files, clear the checkboxes in the Log Activity area.
3. Click OK, then OK to save the changes.
Keep these points in mind:
1 The web activity log continuously adds entries to the file. The entries and files aren't
automatically deleted, and the files can become very large. If you create log files, consider
archiving them on a regular schedule to save hard disk space on your host computer.
1 To maximize security, be sure web users can't view or copy log files by gaining access to the
FileMaker Pro folder.
1 Entries are added to a log file in the order that FileMaker processes them.
1 You can also use FileMaker Pro functions to track user activity. For more information on
functions, see FileMaker
Pro Help.
Securing your data
When you publish a database, it is very important to determine who should have access to the data
and to control which tasks users can perform. For complete information on securing your database,
see the
FileMaker Security Guide, located in the Electronic Documentation folder (inside the
English Extras folder).
Keep these security considerations in mind when publishing databases on the web:
1 User accounts operate the same regardless of which technologies clients use to access your files.
For example, if you create an account that restricts access to deleting records, users who access
the database with that account name and password will not be able to delete records, whether they
access the data from a web browser, an ODBC data source, or another copy of FileMaker Pro.
1 It's safest to create a “web-only” database specifically for web publishing. Make sure the file
contains only the layouts, scripts, and field definitions that you want to expose to the public. For
more information, see the
FileMaker Security Guide.
1 If web users access your files with multiple clients, consider providing them with multiple
accounts. For example, give them an account name and password with more limited access when
accessing the database from a web browser versus another copy of FileMaker
Pro.
1 When enabling Instant Web Publishing for individual files, assign accounts and privilege sets to
web users instead of providing access to all users.
1 If an account limits record-by-record browse privileges but does not limit the privilege to delete
records, it is possible for users to delete records they cannot view.
Web publishing
errors
General information about errors generated when accessing or
interacting with web-shared databases
application.log
Web activity Information about web users’ activities (for example, the users’
IP addresses and pages accessed)
access.log
Select To track In this file