you connect to the Internet with an Internet service provider (ISP), your IP address might be dynamically allocated (it is different each time you connect). A dynamic IP address makes it more difficult for users to locate your databases. If you are not sure of the type of access available to you, consult your ISP or network administrator.
About hosting databases with FileMaker Pro
FileMaker Pro Instant Web Publishing is designed for sharing data in small workgroups, or for accessing your own data on a network. When hosted with FileMaker Pro, Instant Web Publishing can share files with up to five concurrent web users.
About hosting databases with FileMaker Server Advanced
To share information with more simultaneous web users, you can host the databases with FileMaker Server Advanced. FileMaker Server Advanced also provides support for Custom Web Publishing and database connectivity technologies like XML, ODBC, and JDBC. Other benefits of hosting web published files with FileMaker Server Advanced include:
Better support for long running applications Easier maintenance with support for scheduled activities like backups and remote administration Support for hosting more files simultaneously Increased security with SSL encryption
For general information, see Hosting databases with FileMaker Server Advanced: an overview on page 29. For more details, see the FileMaker Server Advanced Custom Web Publishing Guide.
Web publishing improvements
The Instant Web Publishing interface has been redesigned to look and function more like the FileMaker Pro desktop application.
1 You can publish any number of FileMaker Pro layouts directly on the web. You are no longer
restricted by a limited number of predefined web views.
1 Like FileMaker Pro, access to data, layouts, and fields is based on the userss account settings
defined in Accounts and Privileges.
1 Web users can perform complex, multi-step scripts. More than 70 script steps are now supported

on the web.

1 Instant Web Publishing includes a status area with toolbar icons and buttons, providing all the

1 ScriptMaker script steps are now clearly indicated as web compatible; special scripts can
be created for web users. After converting your files, open each script that web users might run and enable Indicate Web Compatibility to see if your scripts contain steps that might produce unexpected results when executed from a web browser.
1 On the web, scripts are always executed with Error Capture on. If your scripts relied on Error
Capture being disabled (off), they may not function the same way. Test your files thoroughly after conversion.
1 Web users can now dynamically choose a layout view to work with data, toggling between Form
View, List View, and Table View. You can limit access to a view in the Views of the Layout Setup dialog box. For more information, see FileMaker Pro Help.
1 FileMaker Pro clients can no longer host databases with Instant Web Publishing. The files must
be web published on the host computer.
1 It is no longer possible to specify the starting and ending points for a range of records in Table
View. Instead, you can specify the starting point and the next 20 records (or remainder of the found set, whichever is smaller) are displayed.
1 Dynamic custom home pages are no longer supported with Instant Web Publishing. However,
you can link to an open database shared with Instant Web Publishing. For more information, see Linking to a database from an HTML page on page 15.
1 The URL syntax has changed for web-published files. If you manually created a link to access a
database on the web, you must update the link after converting the file. For more information, see Linking to a database from an HTML page on page 15.
1 The Web Security databases are no longer supported. If you relied on them for web-based
security, you must transfer the accounts, passwords and associated privileges into your converted database files in FileMaker Pro.
1 Custom Web Publishing is not supported in FileMaker Pro. FileMaker Server Advanced provides
support for Custom Web Publishing, including the delivery of XML data, and other technologies. For more information, visit www.filemaker.com.

5. Repeat steps 3 and 4 for each database you want to publish. 6. Click OK or choose additional settings.
Tip Select Dont display in Instant Web Publishing homepage in the Sharing dialog box to suppress a
filename from appearing in the built-in Instant Web Publishing Database Homepage. This is useful if your solution includes multiple files and you dont want all the filenames displayed. Keep these points in mind:
1 The above instructions are for hosting a database with FileMaker Pro. You may want to host your
files with FileMaker Server Advanced to share your databases with more web users, or to publish more files. For more information, see Hosting databases with FileMaker Server Advanced: an overview on page 29.
1 In Mac OS X, you may be asked to provide the operating system passphrase. For more
information, see Specifying a port number for web publishing on page 13.
1 Assigning access to files in the Instant Web Publishing Sharing dialog box will change the
extended privilege settings in the associated users privilege set. You can review and modify the Extended Privileges settings directly in the Accounts and Privileges dialog box. For more information on setting or modifying access privileges in Accounts and Privileges, see FileMaker Pro Help.
1 You can specify which users can access each file without enabling Instant Web Publishing. 1 The list of open files and file access options in the Sharing dialog box are dimmed if you dont
have Full Access privileges or dont have privileges to manage the extended privileges for a file.
Choosing a language for Instant Web Publishing
You can choose a language for the Instant Web Publishing interface, tooltips, and onscreen Help. Choosing or changing the language has no effect on your actual data.
To specify the language, open the Instant Web Publishing dialog box, select the language to display in the status area, then click OK.
Specifying a port number for web publishing
The TCP/IP address in the Instant Web Publishing dialog box determines where web browsers can find FileMaker Pro databases on the host computer. By default, FileMaker files are shared from port 80. If port 80 is already in use (by a web server or another application), consider changing TCP/ IP Port Number to 591. FileMaker, Inc. has registered port number 591 with the Internet Assigned Numbers Authority (IANA) specifically for web publishing. To specify or change the port number:

Restricting access except to specied IP addresses
You can restrict the IP addresses that can access your databases on the web. For example, you can specify that only web users from the IP address 12.34.5.6 can access your databases. To specify which IP addresses can access your databases:
1. In the Advanced Web Publishing Options dialog box, select Accessible only from these IP
addresses and type the IP address that can access your files. Separate multiple IP addresses with a comma (,).
2. Click OK, then OK to save the changes.
Note Type an asterisk (*) in the section of the IP address to grant access to web users with similar IP addresses (for example: 12.34.5.* or 12.*). You cant type an asterisk in the first section, however.
Disconnecting inactive web accounts
You can specify the amount of time web users remain connected to the database when their session, or connection to the web server, is idle. Sessions are considered idle when web users do not submit requests from the web browser, such as finding, creating, or submitting changes, changing layouts, and so on. A session also becomes idle when the web user closes the web browser window, moves to another web site, or quits the web browser without clicking the Log Out button. To specify the duration that a session can be idle before it times out:
1. Open the Advanced Web Publishing Options dialog box. 2. For Disconnect inactive accounts, specify the amount of time before disconnecting idle web users (from 1 to 60 minutes), then click OK to save the changes.
If you are concerned that web users might not log out of the database properly, specify a short session time out. You can also create a scripted button to automatically log web users off.
See Creating a script to log out of a database and close the session on page 29 and Logging out of a database and closing a web session on page 21 for more information.
Linking to a database from an HTML page
Instead of having web users type the IP address or domain name to access your database, you can create an HTML page that specifies a link to your databases.
To view this Use this link
Database Homepage A particular database
http://<IP address>:<Port number> http://<IP address>:<Port number>/fmi/iwp/cgi?db=<database name>&-loadframes
Keep these points in mind:
1 If you close your files frequently, or if web users access a number of databases, consider linking

You can customize the appearance in a text editing or web authoring application.
1 Choose XML if youd like to transform the table with an XSLT stylesheet.
2. Add links from existing web pages to your new web page. 3. Copy the web pages to your web server.
Static web pages cannot use FileMaker Pro access privileges for protection, but by storing the files in the FileMaker Web folder, you can restrict access by specifying which IP addresses can access the files in the Instant Web Publishing dialog box. For more information, see Restricting access except to specified IP addresses on page 14. For additional security options, see your web server documentation or check with your ISP or network administrator. For more information on exporting records with HTML or XML, see FileMaker Pro Help. Visit www.filemaker.com for general information on XML and example files.
Note The above instructions are for hosting static pages with FileMaker Pro. If you are hosting files with FileMaker Server Advanced, see the FileMaker Server Advanced Web Publishing Installation Guide, included with FileMaker Server Advanced.
Chapter 3 Working with FileMaker databases on the web
FileMaker Pro Instant Web Publishing automatically provides web pages and forms for interacting with your database. Web users click buttons in the status area to browse, find, sort, add, edit, and delete records. When you enable Instant Web Publishing and share files, anyone who has an account for a database and knows the IP address or domain name where it is hosted can access the file. Depending on their account privileges, they can:
view records on different layouts and views add, duplicate, and delete records add and edit data in fields search the database to view a subset of records sort the database to rearrange the records
Important Define accounts and privilege sets to restrict user access to database features for both the

desktop and the web.

Web browser requirements
To work with a published FileMaker Pro database, web users need:
1 Microsoft Internet Explorer, version 6.0 in Windows 98, Windows NT 4.0 with Service Pack 6a
(SP6a) and higher, Windows 2000, Windows XP, or version 5.1 and 5.2 on Mac OS X 10.2.8.
Safari 1.1 on Mac OS X 10.3. access to the Internet or an intranet. the Internet Protocol (IP) address or domain name of the computer that hosts your database file. JavaScript must be enabled in the web browser.
Accessing a FileMaker database from the web
To access the Database Homepage, web users open the web browser, then type the IP address of the host computer.

Type the IP address or domain name in the browser window
1 In some cases, web users can type the domain and host name of your computer instead of the IP
address, for example http://accounts.yourcompany.com. Or, they can type the host name, like http://yourcompany.com. Contact your internet service provider or network administrator for information about mapping a domain and host name to your IP address.
1 If you configure FileMaker Pro to use a port number other than 80 (the default), that port number
must be appended to your IP address, for example: 10.0.0.1:88. See Specifying a port number for web publishing on page 13.
1 You can also create an HTML page that contains a link to a database published on the web. For
more information, see Linking to a database from an HTML page on page 15. The Database Homepage lists the FileMaker Pro databases that are open on the host computer and enabled for web sharing. Web users click a filename to open a database.
Click a filename to open the database
The Database Homepage lists files shared with Instant Web Publishing

Logging into a le

When opening a database, web users may be prompted for their account information.
1 If you have not defined or modified the default accounts for a file, web users must use the default
user account name Admin if prompted to log into a database (unless the Guest account is enabled).
1 If you have not assigned a password for an account, web users only specify the account name. 1 If the Guest account is disabled, then users will be prompted for account name and password
when they open the database.
1 If the Guest account is enabled, and has the Instant Web Publishing privilege set enabled, all web
users automatically open the database with the access privileges assigned to the Guest account. If the Instant Web Publishing privilege is assigned to the Guest account:
1 Web users are not prompted for an account name and password when opening a file. 1 All web users will automatically log in with the Guest account and assume the Guest account
privileges. You can let users change their login accounts from a web browser with the Relogin script step (for example, to switch from the Guest account to another, more full-featured account).

1 If you lock the status area, you must manually create scripts and buttons that offer users all the
necessary functionality. For example, you must create buttons so users can create new records, enter edit mode to modify data, delete records, change layouts, and so on. It is very important to carefully test your database files to make sure you have provided web users access to all critical features.
1 To properly secure your data, you must create a script that logs web users out of the database and
closes the session. For more information, see Creating a script to log out of a database and close the session on page 29.
1 You should provide documentation to help users interact with your data from your custom
environment, as most of the instructions included in the Instant Web Publishing Help file will not be appropriate.
Differences between FileMaker Pro and Instant Web Publishing
The Instant Web Publishing experience is very similar to using the FileMaker Pro desktop application. Web users can change modes, choose layouts and views, and much more.
Benets to accessing databases with Instant Web Publishing
There are some unique advantages to the Instant Web Publishing feature in FileMaker Pro:
1 You can easily and quickly deploy a solution onto the web with your existing database. You dont
need to use web authoring tools, write HTML or CSS code, or use other technologies to share your data with anyone using a compatible web browser.
1 You can access data remotely, whether from a home office or while travelling. 1 By hiding and locking the status area, you can easily deploy a custom, web-based application. Benets to accessing databases with FileMaker Pro
Although accessing a database from the web is very similar to FileMaker Pro, it is not as responsive as accessing a database from a FileMaker Pro network client:
1 There are no customization features available on the web. Although web users can choose layouts
and different layout views, they cannot add, delete, or modify fields, layouts, scripts, relationships, and so on.
1 Web users cannot directly interact with the hard drive, so import/exporting data, drag and drop,
and automation with OLE, ActiveX, and Apple events will not work.
1 Web users can only enter data in text, number, date, or time fields; they cannot enter or modify
container field objects like images, sounds, and QuickTime files.
Web users cannot enter data with rich text formatting (RTF). Web users cannot view and print complex, multi-page reports. Web users cannot spell check their data. Web users should only interact with a database from one web browser window. FileMaker Pro keyboard commands are not available for use in the web browser.
Chapter 4 Designing a database for Instant Web Publishing

1 When hosting a database with FileMaker Server Advanced, only use plug-ins that have been
enabled for the FileMaker Server Web Publishing Engine. (In general, a plug-in designed for use only with FileMaker Pro will not be compatible with the Web Publishing Engine.) For information on installing plug-ins on FileMaker Server Advanced, see the FileMaker Server Advanced Web Publishing Installation Guide, included with FileMaker Server Advanced.
1 You should not access the same file from multiple browser windows.
Working with graphics, sounds, and movies on the web
When you publish a database on the web with Instant Web Publishing, web users can work with data in container fields in limited ways:
1 Web users can't play sounds or display OLE objects in a container fielda graphic is displayed

instead.

1 Web users can't add graphics, sounds, or movies to a container field.
Important Images can either be stored inside the database itself or, for best performance, stored as
file reference using a relative path. If youre hosting the database with FileMaker Pro, referenced image and movie files must be stored in the Web folder, in the FileMaker Pro folder.
Setting the initial layout and view
When a FileMaker Pro database is set to perform a script at startup, users who access the database through Instant Web Publishing can see the results of that script each time they open the database.
By setting a startup script, you can determine which layout and view web users see when they open the database with the following script steps:
1 Go to Layout [Layout Name] 1 Enter Browse Mode [ ] 1 View As [Form View]
You can also specify a starting layout in the File Options dialog box. See FileMaker Pro Help for more information.
Hiding the status area to customize the interface
FileMaker Pro automatically generates interface controls in the status area for interacting with databases shared with Instant Web Publishing. These controls allow the user to create, alter, and delete records; switch views and modes when accessing databases via a web browser; find and sort records; open HTML Help; and so on. If you want to present your own interface for performing all database tasks, you can create a script that hides the status area when opening the file. To suppress Instant Web Publishing controls, create a startup script that includes Toggle Status Area [Hide] as one of the first steps. For solutions involving multiple database files, use this startup script step in each file.

Important When you suppress the FileMaker Pro Instant Web Publishing controls, web users are
completely dependent on your scripted buttons. You must include a button that lets web users log out of the solution, as well as perform other tasks. See Creating a script to log out of a database and close the session on page 29 for details. You can include scripted buttons on your layout to:
add, select, navigate, edit, and delete records. specify search criteria and perform find requests. sort the database in all desirable ways. change layouts and layout views. continue or cancel scripts that may have paused. open other database files (the databases must be open and shared with Instant Web Publishing on the host computer).
Important If you are suppressing the status area, thoroughly test your database to make sure you have provided users all required functionality.
Specifying the sort order for web users
With Instant Web Publishing, you no longer specify sort fields on a prescribed layout. Web users can now sort data based on fields on the current layout. To control which fields web users can sort on, you can:
1 restrict access to layouts with the users account in Accounts and Privileges. 1 hide the status area and create buttons that are scripted to sort the data by fields specified in the

script.

Scripts and Instant Web Publishing
The ScriptMaker feature in FileMaker Pro is useful for automating frequently performed tasks, or for combining several tasks. When used in Instant Web Publishing, it can allow web users to perform more tasks, or to easily perform a series of tasks simply by clicking a button. FileMaker Pro now supports over 70 script steps with Instant Web Publishing and Custom Web Publishing. Web users can perform a variety of automated tasks when you provide buttons on your FileMaker Pro layouts or set scripts to run when a database is opened or logged out. To see script steps that are not supported, select the Indicate Web Compatibility checkbox in the Edit Script dialog box. Dimmed script steps are not supported on the web. For information on individual script steps, see FileMaker Pro Help.
Select Indicate web compatibility to dim script steps that are not web-compatible

Script steps tips and considerations
Although many script steps work identically on the web, there are several that work differently due to design limitations. Before sharing your database, evaluate all scripts and buttons that will be executed from a web browser. Be sure to log in with different user accounts to make sure they work as expected for all clients. Keep these tips and considerations in mind:
1 Use accounts and privileges to restrict the set of scripts that a web user can execute. Verify that
the scripts contain only web-compatible script steps, and only provide access to scripts that should be used from a web browser.
1 Consider the side effects of scripts that execute a combination of steps that are controlled by
access privileges. For example, if a script includes a step to delete records, and a web user does not log in with an account that allows record deletion, the script will not execute the Delete
Records script step. However, the script might continue to run, which could lead to unexpected results.
1 In scripts, you can select Run script with full access privileges to allow scripts to perform tasks that
you would not grant individuals access to. For example, you can prevent users from deleting records with their accounts and privileges, but still allow them to run a script that would delete certain types of records under conditions predefined within a script.
1 If your scripts contain steps that are unsupported, for example, steps that are not web-compatible,
use the Allow User Abort script step to determine how subsequent steps are handled.
1 If the Allow User Abort script step option is enabled (on), unsupported script steps will stop the

script from continuing.

1 If Allow User Abort is off, unsupported script steps are skipped over and the script continues to

execute.

1 If this script step is not included, scripts are executed as if the feature is enabled, so unsupported
script steps will stop scripts.
1 Some scripts that work with one step from a FileMaker Pro client may require an additional
Commit Record/Request step to save the data to the host. Because web users dont have a direct connection to the host, they arent notified when data changes. For example, features like conditional value lists arent as responsive for web clients because the data must be saved to the host before the effects are seen in the value list field.

1 Similarly, any script that modifies data should include the Commit Record/Request step, because
all data changes arent visible in the browser until the data is saved, or submitted to the server. This includes several script steps like Cut, Copy, Paste, and so on. Many single-step buttons should be converted into scripted buttons to include the Commit Record/Request step. When designing scripts that will be executed from a web browser, its a good idea to include the Commit Record/Request step at the end of a script to make sure all changes are saved.
1 To create conditional scripts based on the type of client, use the Get [ApplicationVersion]
function. If the value returned includes Web Publishing you know that the current user is accessing your database with Instant Web Publishing. For more information on functions, see FileMaker Pro Help.
1 Because there are intermediary technologies involved when accessing a FileMaker Pro database
from a web browser, you must assess the activities on the web server before closing a file. Some scripts open additional windows in the virtual FileMaker environment on the web server, and they must be closed before the session can be terminated. Any open windows will be closed automatically if web users click the Log Out button or when the session times out. For more information, see Creating a script to log out of a database and close the session, below.
1 After converting your files, you should open each script that web users might run and enable
Indicate Web Compatibility to ensure that the script will execute properly with Instant Web Publishing.
The script steps below function differently on the web than in the desktop application. For information on all script steps, see FileMaker Pro Help.
Script step Behavior in Instant Web Publishing
Perform Script Exit Application Allow User Abort
Scripts cannot perform in other files, unless the files are open and shared with Instant Web Publishing on the host or server machine. Closes all windows, ends the users session, and takes the user back to the Database Homepage. Determines how unsupported script steps are handled. Enable to stop scripts from continuing, and disable to skip over unsupported steps. See above for more details. This is always enabled with Instant Web Publishing, and prevents web users from aborting scripts. The script pauses until the user clicks Resume or executes the Resume script step by clicking a scripted button, or the session times out. Sorts must be saved with the script to execute in Instant Web Publishing. Opens a complete URL from a text or calculation field in a new browser window (URL must contain http:// if the target URL starts with http://). You cannot use Go to Field to make a particular field active in the web browser, but you can use this script in conjunction with other script steps to perform tasks. For example, you can go to a field, copy the contents, go to another field and paste the value. To see the effect in the browser, be sure to save the record with the Commit Record script step.

Mac OS X: choose FileMaker Pro menu > Sharing > Instant Web Publishing.
2. For Advanced Options, click Specify, then enable the log files you want to create.
Select To track In this file

Script errors

Information about errors generated when web users execute application.log scripts (for example, it documents script steps that are skipped if theyre not web-compatible)

Select

To track

In this file

Web publishing errors Web activity
General information about errors generated when accessing or interacting with web-shared databases
Information about web users activities (for example, the users
application.log access.log
IP addresses and pages accessed)
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.
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.

session, logging out 21 sort order, specifying 26 specifying access 14 SSL encryption 7, 21 static IP address 15 static publishing 15 status area changing language in 12 hiding 21, 26
Table View designing for 24 differences with FileMaker 24 restrictions 9 setting properties 24 TCP/IP port number 13 testing your published database 31 third party plug-ins 25 with FileMaker Server Advanced 25 time out setting 14, 21
Relogin script 18 requirements web browser 17 web publishing 6
scripts Accounts and Privileges 27 Change Password 19 for web users 8 in Instant Web Publishing 29 log out 29 Relogin 18 testing 31 tips and considerations 27 using Error Capture 9 using in Instant Web Publishing 27 searches, extending and constraining 8 security Accounts and Privileges 8 considerations 32 data access 32 document and data storage 33 FileMaker Server Advanced 7 guidelines 5 restricting access 14 restricting web access 14 reviewing script steps 33 SSL encryption 7 with multiple accounts 32 with static web pages 16
URLs, link to Database Homepage 15
web browser publishing requirements 6 requirements 17 web pages, viewing databases in 17 Web Security databases, not supported 9, 33 Web Styles no longer supported 8 web users accessing databases 19 assigning access to files 12 default login account 18 limitations of FileMaker Pro 22 maximum number 21 new scripts 8 tracking activity 32 Windows web browser requirements 17 web publishing requirements 7
XML exporting 16 XSLT stylesheets 5, 16

Access privileges for web users can be set to allow execution of specific, individual scripts and prevent execution of others. ScriptMaker script steps are clearly indicated as web compatible; special scripts can be created for web users. After converting your files, open each script that web users might run and enable Indicate web compatibility to see if your scripts contain steps that might produce unexpected results when executed from a web browser. On the web, scripts are always executed with Set Error Capture on. If your scripts relied on Set Error Capture being disabled (off), they may not function the same way. Test your files thoroughly after conversion.
Web users can dynamically choose a layout view to work with data, toggling between Form View, List View, and Table View. You can limit access to a view in the Views of the Layout Setup dialog box. For more information, see FileMaker Pro Help.
FileMaker Pro clients can no longer host databases with Instant Web Publishing. The files must be web published on the host computer. It is no longer possible to specify the starting and ending points for a range of records in Table View. Instead, you can specify the starting point and the next 50 records (or remainder of the found set, whichever is smaller) are displayed. The URL syntax has changed for web-published files. If you manually created a link to access a database on the web, you must update the link after converting the file. For more information, see Linking to a database from an HTML page on page 15. The Web Security databases are no longer supported. If you relied on them for web-based security, you must transfer the accounts, passwords and associated privileges into your converted database files in FileMaker Pro.
With FileMaker Pro, it is easy to share your database on the web dynamically with Instant Web Publishing, or statically, by exporting data as HTML or XML. If you are connected to a LAN or WAN, you can share your file without requiring additional software. To share files over the internet, contact an Internet Service Provider (ISP) for internet access and information about hosting a database.

Changing the port number on Mac OS X The first time you enable Instant Web Publishing, Mac OS X requests permission to make a one-time change to your computers setting to facilitate web publishing on a port number below 1024. For security reasons, Mac OS X restricts access to ports below 1024. To configure FileMaker Pro to use ports below 1024, you must provide an administrator password, such as the passphrase created when you first set up Mac OS X. You do not need an administrator password to use a port number between 1024 and 65535. For more information on creating an account with administrator privileges, see the Mac OS X Help system.
Checking the maximum number of web connections
The number of simultaneous web users allowed to access your files depends on which application you use to host your database. With FileMaker Pro, you can host up to five concurrent web users. Use FileMaker Server Advanced to share files with more web users. To view the maximum number of web connections allowed:
1. Open the Instant Web Publishing dialog box (see Sharing a database with Instant Web Publishing on page 11). 2. For Advanced Options, click Specify, then view the Maximum number of connections number. 3. Click OK, then OK.
When the maximum number is reached, additional web users see an error message in the web browser when they try to access the database. Important If you feel that you have reached the maximum number of users inappropriately, its possible that a web user has not logged out of the database properly. You can wait for the sessions to time out or close the file to disconnect web users from the database. For more information, see Logging out of a database and closing a web session on page 24.
Restricting access except to specified IP addresses
You can restrict the IP addresses that can access your databases on the web. For example, you can specify that only web users from the IP address 12.34.5.6 can access your databases. To specify which IP addresses can access your databases:
1. Open the Instant Web Publishing dialog box (see Sharing a database with Instant Web Publishing on page 11). 2. For Advanced Options, click Specify. 3. Select Accessible only from these IP addresses and type the IP address that can access your files. Separate multiple IP addresses with a comma (,). 4. Click OK, then OK to save the changes.

Working with records that contain a web viewer
Web users can interact with web viewers in much the same way FileMaker Pro desktop users can. Web users can:
view web page content that is related to the current record including content that requires a web browser plug-in, such as PDF documents, QuickTime movies, and so on click links to navigate web sites use the shortcut menu within a web viewer to move back and forward between web pages, copy text, and so on
Note To navigate back and forward within a web viewer in Instant Web Publishing, use the shortcut menu. Right-click (Windows) or Control-click (Mac OS) within the web viewer and choose Back or Forward. If the layout has more than one web viewer, the shortcut menu works only with the web viewer that has most recently changed from one page to another, not necessarily the one that your mouse pointer is over.
Logging out of a database and closing a web session
Important When web users are finished working with a database, it is important that they click the Log Out button in the status area and quit the web browser application. If they close browser windows or quit the browser application before logging out, their session is still open. This might:
prevent others from accessing the data make data vulnerable to hackers until the specified time out occurs
If this happens, you can either wait for the session to time out or close the file on the host machine, which immediately disconnects all web users. There is no way to send a message to web users requesting that they log out of their sessions. If you are concerned that web users might not log out of the database properly, you can set the session time out for a short amount of time. This minimizes the inconvenience if web users dont log out of the database properly. See Disconnecting inactive web accounts on page 15 for more information. You can also create a scripted button to safely log web users off. See Creating a script to log out of a database and close the session on page 36. If you are concerned about security, consider hosting the files with FileMaker Server and enable SSL encryption in a web browser. For more information, see the FileMaker Pro Users Guide or FileMaker Server Help.

Displaying a database with the status area hidden
Like the desktop version of FileMaker Pro, you can create a script that hides and locks the status area when the database is opened in a web browser. This allows you to design a custom interface. Keep these points in mind:
If you lock the status area, you must manually create scripts and buttons that offer users all the necessary functionality. For example, you must create buttons so users can create new records, enter edit mode to modify data, delete records, change layouts, and so on. It is very important to carefully test your database files to make sure you have provided web users access to all critical features. To properly secure your data, you must create a script that logs web users out of the database and closes the session. For more information, see Creating a script to log out of a database and close the session on page 36. You should provide documentation to help users interact with your data from your custom environment, as most of the instructions included in the Instant Web Publishing Help file will not be appropriate.
Differences between FileMaker Pro and Instant Web Publishing
The Instant Web Publishing experience is very similar to using the FileMaker Pro desktop application. Web users can switch between finding and editing modes, choose layouts and views, and much more.
Benefits to accessing databases with Instant Web Publishing
There are some unique advantages to the Instant Web Publishing feature in FileMaker Pro:
You can easily and quickly deploy a solution onto the web with your existing database. You dont need to use web authoring tools, write HTML or CSS code, or use other technologies to share your data with anyone using a compatible web browser. You can access data remotely, whether from a home office or while travelling. By hiding and locking the status area, you can easily deploy a custom, web-based application.
Benefits to accessing databases with FileMaker Pro
Although accessing a database from the web is very similar to FileMaker Pro, it is not as responsive as accessing a database from a FileMaker Pro network client:
There are no customization features available on the web. Although web users can choose layouts and different layout views, they cannot add, delete, or modify fields, layouts, scripts, relationships, and so on. Web users cannot directly interact with the hard drive, so import/exporting data, drag and drop, and automation with OLE, ActiveX, and Apple events will not work. Web users can only enter data in text, number, date, time, or timestamp fields; they cannot enter or modify container field objects like images, sounds, and QuickTime files. Web users cannot enter data with rich text formatting (RTF). Web users cannot view and print complex, multi-page reports. Web users cannot spell check their data. Web users should only interact with a database from one web browser window. FileMaker Pro keyboard commands are not available for use in a web browser. Tooltips created in FileMaker Pro Advanced that are displayed in a web browser are updated only when a page is loaded. Web users cannot use scripted Back and Forward buttons to navigate within a web viewer. However, web users can choose Back and Forward from the shortcut menu in a web viewer. Even if you clear Allow interaction with web viewer content, web users might still be able to interact with a web viewer in a limited way. Web users experience longer download times in List View when browsing records that display web viewers.

With FileMaker Pro, data displayed on a web form with Instant Web Publishing looks and behaves similarly to a FileMaker layout. When you design solutions that are accessed on the web, there are some limitations of the technologies that you should be aware of. For example, FileMaker Pro layouts are rendered on the web using Cascading Style Sheets, which doesnt offer graphics support as robust as the FileMaker Pro application.
Tips for designing layouts for Instant Web Publishing
FileMaker Pro layouts determine which fields web users see, and how the data is formatted.
Like FileMaker Pro, default web layouts can be specified with startup scripts. User accounts and privileges determine which layouts web users can view. Web users can only search on fields that are present on the current layout. If youre designing layouts specifically for searching, note that web users cant enter search criteria for summary, global, or container fields.
Tips for rendering layouts in Instant Web Publishing
Layouts are rendered in web browsers using Cascading Style Sheets (CSS). Not all layout objects can display with CSS. For example:
Avoid diagonal lines, pen patterns, fill patterns, and ovals. They do not display in web browsers. Rounded objects created with FileMaker Pro tools cannot be rendered. For example:
Rounded rectangles are displayed as rectangles. Buttons and tabs on tab panels are displayed as rectangles (without rounded corners). Circles are not displayed.
However, Instant Web Publishing can display an image of a rounded object. You can use FileMaker Pro layout tools to draw a rounded object, use the screen-capture feature of your operating system to create an image of the object, then paste or insert the image onto your FileMaker Pro layout. This alternative doesnt work for rounded tabs, though.
Complex or layered pictures are not rendered properly. Its best to create composite pictures in a drawing program, then paste the image into the FileMaker Pro layout. If your images have transparent components, use the GIF file format. For forms and reports, make fields large enough to display and print the data. In the web browser, fields do not expand when they are active. You can format fields to display a scroll bar so users can view the field contents. A timestamp field should not be formatted to display a drop-down calendar. The calendar and optional calendar icon are not displayed for timestamp fields in Edit and Find modes. Arrange fields formatted as a checkbox set or radio button set with the value lists displayed horizontally for best results.

Radio buttons and checkboxes display as standard HTML controls. If they are getting cropped, enlarge the fields on the FileMaker Pro layout. Buttons can display multiple lines of text if you include Return characters between the lines. Make sure the button is large enough to accommodate the text in supported web browsers. Instant Web Publishing offers limited text styles. Paragraph text styles, tab stops, and vertical alignment are not supported. Additionally, underline, word underline and double underline are all rendered as regular underline. Evaluate your layouts in all supported web browsers before sharing the database with others. If layout text is wrapping to a new line, increase the size of the text boundaries in the FileMaker Pro layout. For example, if the text is aligned left, drag the lower right handle slightly towards the right. The FileMaker Pro Title Header, Title Footer, and Summary layout parts are not supported and should be removed from layouts used with Instant Web Publishing. To avoid cropping of movies, make sure the container field is large enough to display the movie and the movie controls. Avoid using more than one copy of the same field on a layout. Otherwise, web users must change all copies of the field to save changes or to perform a find. Conditional formatting does not appear in Instant Web Publishing.
Design considerations for List View and Table View
With Instant Web Publishing, users can dynamically choose a layout view to interact with data on the current layout (provided that you make the layout view available in the Layout Setup dialog box). The key differences between views in FileMaker Pro and Instant Web Publishing are:
List View displays 25 records at a time and Table View displays 50. The current record is always at the top, or the first row. When new records are created, they become the current record. You can display previous record ranges with the controls in the status area. Web users can add, edit, and delete records and find requests in List View and Table View. In Table View, records can be sorted in ascending or descending order by clicking the column heading (the field name). Sorting is enabled in the Table View Properties section of the Layout Setup dialog box. For more information, see FileMaker Pro Help.
Tips for working with data in a web browser
Formatting for date, time, timestamp, and number fields is specified in the layout. Repeating field data is displayed in web browsers. The tab order defined for fields in a layout works in Instant Web Publishing. However, fields can only be tabbed to while in Edit or Find mode. Tab controls and buttons are not included in the tab order in Instant Web Publishing. Note The tab order in a web browser might vary from the tab order in FileMaker Pro. Different browsers might support the tab order in a different manner.

Setting the initial layout and view
When a FileMaker Pro database is set to perform a script at startup, users who access the database through Instant Web Publishing can see the results of that script each time they open the database. By setting a startup script, you can determine which layout and view web users see when they open the database with the following script steps:
Go to Layout [Layout Name] Enter Browse Mode [ ] View As [Form View]
You can also specify a starting layout in the File Options dialog box. See FileMaker Pro Help for more information.
Hiding the status area to customize the interface
FileMaker Pro automatically generates interface controls in the status area for interacting with databases shared with Instant Web Publishing. These controls allow the user to create, alter, and delete records; switch views and modes when accessing databases via a web browser; find and sort records; open HTML Help; and so on. If you want to present your own interface for performing all database tasks, you can create a script that hides the status area when opening the file. To suppress Instant Web Publishing controls, create a startup script that includes Show/Hide Status Area [Hide] as one of the first steps. For solutions involving multiple database files, use this startup script step in each file. If you want to prevent web users from being able to create new records, you can either:
create a script to hide the status area. prevent creation of new records with a users account in Accounts & Privileges.
Important When you suppress the FileMaker Pro Instant Web Publishing controls, web users are completely dependent on your scripted buttons. You must include a button that lets web users log out of the solution, as well as perform other tasks. See Creating a script to log out of a database and close the session on page 36 for details. You can include scripted buttons on your layout to:
add, select, navigate, edit, and delete records. specify search criteria and perform find requests. sort the database in all desirable ways. change layouts and layout views. continue or cancel scripts that may have paused. open other database files (the databases must be open and shared with Instant Web Publishing on the host computer).
Important If you are suppressing the status area, thoroughly test your database to make sure you have provided users all required functionality.
Specifying the sort order for web users
Web users can sort data based on fields on the current layout. To control which fields web users can sort on, you can:
hide the status area and create buttons that are scripted to sort the data by fields specified in the script. restrict access to layouts with a users account in Accounts & Privileges.

Web viewer design considerations
If your FileMaker Pro solution contains web viewers, consider the following points for Instant Web Publishing:
Content in a web viewer may have unintended effects on Instant Web Publishing. Therefore you must test the websites you want to display within a web viewer. For example, a URL (either a URL calculated from field data or a URL that the user specifies by clicking a link in a web viewer) can specify a page that has the target=top attribute. This attribute causes the page to completely replace Instant Web Publishing in the web browser window. Web users might be able to interact with web viewer content in a limited way, even if you clear the Allow interaction with web viewer checkbox in the Web Viewer Setup dialog box. Limited interaction can also occur even if a web viewer is defined as a button. Web pages that load code such as JavaScript or references to Java, ActiveX, Flash, or other plug-ins run that code within the users web browser. Some web technologies may not be supported or may be supported differently in the browsers supported by Instant Web Publishing. Security settings within the users browser may also prevent the use of these plug-ins. If the URL calculated by a web viewer does not include a colon (:), then Instant Web Publishing automatically adds the scheme http:// to the beginning of the URL. To avoid errors, include the appropriate scheme in the web address when you set up a web viewer. The Back and Forward actions of the Set Web Viewer script step are not supported in Instant Web Publishing. See Script steps tips and considerations on page 33. Web users can use the shortcut menus Back and Forward commands instead. However, if a layout has more than one web viewer, the shortcut menu works only with the web viewer that has most recently changed from one page to another, not necessarily the one that your mouse pointer is over. Instant Web Publishing does not support web viewers whose content is itself published by Instant Web Publishing. No web page displays in a web viewer if the web viewer URL contains /fmi/iwp.
There might be other ways in which web viewers behave differently for web users and FileMaker Pro users. Additionally, web viewers might behave differently in the different web browsers supported by Instant Web Publishing. For the latest information on web viewers, see www.filemaker.com/support/technologies.

The hasFocus, containsFocus, source and content attributes return values that were current when the web browser most recently loaded the page. That is, these attributes arent updated after the user clicks or tabs into an object, edits data without submitting it, navigates to other web pages within a web viewer, and so on. When this function acts on a web viewer, the content and source attributes return the same value, a URL.
For more information on the GetLayoutObjectAttribute function, see FileMaker Pro Help.

Script Steps

The script steps below function differently on the web than in the desktop application. For information on all script steps, see FileMaker Pro Help.
Script step Behavior in Instant Web Publishing
Perform Script Allow User Abort Set Error Capture Pause/Resume Script Sort Open URL Go to Field Commit Records/Requests New Window
Scripts cannot perform in other files, unless the files are open and shared with Instant Web Publishing on the host or server machine. Determines how unsupported script steps are handled. Enable to stop scripts from continuing, and disable to skip over unsupported steps. See above for more details. This is always enabled (On) with Instant Web Publishing. Therefore, alert messages are always suppressed when scripts are run. The script pauses until the user clicks Continue or executes the Resume script step by clicking a scripted button, or the session times out. Sorts must be saved with the script to execute in Instant Web Publishing. Opens a complete URL from a text or calculation field in a new browser window (URL must contain http:// if the target URL starts with http://). In Browse mode, switches a record into editing mode and sets the insertion point in the specified field. Submits the record to the database. Does not open a new physical browser window, but instead opens a new virtual window within the existing browser window. Although each virtual window can display a different layout, table, found set, or sort order as is possible in FileMaker Pro windows, web users can only view one virtual window at a time. Brings the specified virtual window to the front. Closes the specified or current virtual window to reveal the window underneath it. Lets the user log into the database using a different account and password without closing and reopening the file. However, for web users you must select the Perform without dialog checkbox and specify an account name and password in this script step. Updates the content area of the browser window. Select Flush cached join results to update the display of dynamic or complex related field content. The Reset action resets a web viewer to its originally specified web address, but it does not clear the web viewers Back and Forward history. The Reload action reloads the web page using the most recently set URL. This URL is either the one initially defined for the web viewer or the one most recently set with the Go to URL action, not necessarily the URL of the currently displayed web page. When using the Go Back and Go Forward actions, Set Web Viewer behaves as an unsupported script step as described above. For these actions, the web viewer displays the web page of the most recently set URL and the Get(LastError) function returns Command is unknown.

Select Window Close Window Re-Login
Refresh Window Set Web Viewer

Exit Application

Closes all virtual windows, ends the users session, and takes the user back to the Database Homepage.
Creating a script to log out of a database and close the session
It is important that web users properly close their session by clicking the Log Out button in the status area. If they close browser windows or quit the browser before clicking the Log Out button, their session is still open. This might prevent others from accessing the database and could make data vulnerable to hackers until the specified time out occurs. Important Your script should include the Exit Application script step, which closes all virtual windows, ends the users session, and takes the user back to the Database Homepage.
Hosting databases with FileMaker Server Advanced: an overview
Without planning, you might have to redefine links to other files or images. If your database is maintaining file path information for container field objects or file relationships, you should store the file paths as a relative link. Its also best to store all files in the same folder. Here are general steps for hosting Instant Web Publishing files with FileMaker Server Advanced:
1. Move the FileMaker Pro databases into the Databases folder in the FileMaker Server folder. 2. Move the contents of the Web folder to the root folder of the web server software. Make sure the relative path is preserved.
For IIS, move the files to: <root drive>\Inetpub\wwwroot For Apache, move the files to: /Library/WebServer/Documents Note Verify the path with the server administrator.
3. Redirect your URLs to: http://<IP address>/fmi/iwp or http://<domain name>/fmi/iwp so web users can locate your database.
For information on enabling Instant Web Publishing in FileMaker Server Advanced, see FileMaker Server Help.
Documenting your solution
Instant Web Publishing cannot cover the nuances of how web users should interact with your particular databases. Its helpful if you can provide your own documentation, especially if youre presenting a lot of layouts and automating tasks with scripted buttons. You should include the following information in your documentation:
Browsing and finding records: Let web users know that they work with data in Browse mode or Find mode. Instruct users how to create, edit, delete, find, and sort records. Navigating the database: Instruct web users on how to view records in appropriate layouts and layout views. It is important that web users properly close their session, or connection to the host computer, by clicking the Log Out button in the status area. For more information, see Logging out of a database and closing a web session on page 24. Tooltips created in FileMaker Pro Advanced for layout objects can help web users understand how to interact with your solution.Tooltip text will appear in a web browsers default text style. Note Tooltips are updated only when a page is loaded. For more information on tooltips, see FileMaker Pro Help.

Before notifying users that your published database is available, it is important to verify that it looks and functions as you expect.
Test features like finding, adding, deleting, and sorting records with different accounts and privilege sets. Verify that various privilege sets are performing as expected by logging in with different accounts. Make sure unauthorized users cant access or modify your data. Click all scripted buttons to verify that the outcome is expected. See Scripts and Instant Web Publishing on page 33 for information on designing web-friendly scripts. Test your published database with different operating systems and browsers. If the web pages arent displaying properly, see Web browser requirements on page 19 and review chapter 4, Designing a database for Instant Web Publishing.
Testing your database with a network connection
To access a published database, open web browser software, type the IP address or domain name of the host computer and press Return or Enter. You can view an IP address in the Instant Web Publishing dialog box. For more information, Accessing a FileMaker database from the web on page 20.
Testing your database without a network connection
If you dont have a network connection, you should still test your database in all compatible web browsers. Open the web browser software and type http://localhost/ or http://127.0.0.1/ and press Return or Enter. The Database Homepage should display a list of all open database files that have Instant Web Publishing enabled. If you dont see an open, shared database listed, see Accessing a FileMaker database from the web on page 20 for more information.
Monitoring web activity with log files
You can set logging options to track the activity your database receives from web users. When you enable the log files, FileMaker creates log files in the FileMaker Pro 9/Web logs folder. You can view them in any application that opens text files. To create log files:
1. Choose File menu > Sharing > Instant Web Publishing.
2. For Advanced Options, click Specify, then enable the log files you want to create.
Select To track In this file

Script errors

Chapter 5

Testing, monitoring, and securing your site
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. If the same account opens related files, the related data is displayed on layouts containing related fields. Instant Web Publishing uses the accounts and privilege sets defined in FileMaker Pro for the best security. For more information, see the FileMaker Pro Users Guide. Never store sensitive documents or databases inside the Web folder. With FileMaker Pro, you can put images to share with container fields or static HTML pages that you want to publish in the Web folder inside the FileMaker Pro folder, but due to web server architecture, all files in the Web folder are accessible and might be deleted by others. Carefully review your scripts to make sure they are web compatible and that the combination of steps dont produce unexpected results. For more information, see Scripts and Instant Web Publishing on page 33. As operating system vendors continue to patch security problems, they may disable certain features, often in conjunction with security settings within the users web browser. Such changes might disable or change the behavior of web viewers in Instant Web Publishing. If such changes affect your solution, FileMaker recommends that you tell users how to change security settings in their browsers to allow web viewers to function properly, or ensure that the URLs used by your web viewers are for only trusted web sites.
access privileges See Accounts and Privileges account names and passwords, character set restrictions 29 Accounts and Privileges Guest account 21 limiting layouts 27 scripts 33 setting 12 testing 37 ActiveX 26 Allow User Abort script step 34, 35 Apache, hosting Instant Web Publishing databases 36 Apple events 26 authentication external SQL data sources 30 forms-based in IWP 21 Custom Web Publishing, in FileMaker Server Advanced 5
data modification, script step 34 data modification, script steps 34 Database Homepage hiding files on 12 linking to 15 databases enabling Instant Web Publishing 7, 11, 19 linking to 15 restricting access 14 static web publishing 16 testing before publishing 37 Delete Records script step 33 disconnect idle accounts 15 setting time out 15 documentation custom environments 25 Instant Web Publishing Help 22 Drop-down Calendar field format 30

URLs, link to Database Homepage 15

View As script step 30

web browser open database URL 15 publishing requirements 7 requirements 19 web pages, viewing databases in 19 Web Security databases, not supported 9 Web Styles, not supported 8 web users accessing databases 22 assigning access to files 12 limitations of FileMaker Pro 26 maximum number of connections 24 tracking activity 38 web viewers 8 design considerations 32 limitations for web users 26 security 39 working with 24 Windows web browser requirements 19 web publishing requirements 7
XML exporting 17 XSLT stylesheets 17 XML, XSLT, PHP 5