FileMaker 7

Instant Web Publishing Guide
2004 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker is a trademark of FileMaker, Inc., registered in the U.S. and other countries, and ScriptMaker and the file folder logo are trademarks of FileMaker, Inc. FileMaker documentation is copyrighted. You are not authorized to make additional copies or distribute this documentation without written permission from FileMaker. You may use this documentation solely with a valid licensed copy of FileMaker software.
All persons and companies listed in the examples are purely fictitious and any resemblance to existing persons and companies is purely coincidental. Credits are listed in the Acknowledgements document provided with this software. For more information, visit our web site at www.filemaker.com. Edition:01

Contents

Chapter 1
About publishing FileMaker Pro databases on the web
About this guide Web publishing requirements Connecting to the Internet or an intranet About hosting databases with FileMaker Pro About hosting databases with FileMaker Server Advanced Web publishing improvements Publishing files from previous versions of FileMaker Pro Chapter 2
Publishing your database on the web
Sharing a database with Instant Web Publishing Choosing a language for Instant Web Publishing Specifying a port number for web publishing Checking the maximum number of web connections Restricting access except to specified IP addresses Disconnecting inactive web accounts Linking to a database from an HTML page Publishing FileMaker Pro data on static web pages General steps for publishing static data Chapter 3
Working with FileMaker databases on the web
Web browser requirements Accessing a FileMaker database from the web Logging into a file Working with data in Instant Web Publishing Viewing and modifying records in Browse mode Finding records Logging out of a database and closing a web session Displaying a database with the status area hidden Differences between FileMaker Pro and Instant Web Publishing Benefits to accessing databases with Instant Web Publishing Benefits to accessing databases with FileMaker Pro

Chapter 4

Designing a database for Instant Web Publishing
Tips for designing layouts for Instant Web Publishing Tips for rendering layouts in Instant Web Publishing Design considerations for List View and Table View Tips for working with data in a web browser General database design considerations Working with graphics, sounds, and movies on the web Setting the initial layout and view Hiding the status area to customize the interface Specifying the sort order for web users Scripts and Instant Web Publishing Script steps tips and considerations Creating a script to log out of a database and close the session Hosting databases with FileMaker Server Advanced: an overview Documenting your solution Chapter 5
Testing, monitoring, and securing your site
Testing your database with a network connection Testing your database without a network connection Monitoring web activity with log files Securing your data Index
Chapter 1 About publishing FileMaker Pro databases on the web
With FileMaker Pro, you can display your databases on the web in a variety of ways. This makes your data:
1 available to many people using a compatible web browser, anywhere in the world. (You can,
however, restrict access to files.)
1 accessible from many locations, for example, while traveling or working remotely.
There are three ways to publish your data using FileMaker Pro. Instant Web Publishing: With Instant Web Publishing, you can quickly and easily publish your database on the web. You dont need to modify your database files or install additional software anyone with compatible web browser software and access to the Internet or an intranet can connect to your database to view, edit, sort, or search records, if you give them access privileges. You can use additional software to perform additional tasks, for example, to configure a firewall to secure your network. Static publishing: If your data rarely changes, or if you don't want users to have a live connection to your database, you can use static publishing. With static publishing, you export FileMaker Pro data to create a web page that you can further customize with HTML. The web page doesn't change when information in your database changes, and users don't connect to your database. (With Instant Web Publishing, data is updated in a web browser window each time the browser sends a request to FileMaker Pro.) For more information, see Publishing FileMaker Pro data on static web pages on page 15. Custom Web Publishing: For more control over the appearance and functionality of your published database, use the Custom Web Publishing technologies available in the FileMaker Server Advanced software. With XML and XSLT stylesheets, you can:

1 Integrate your database with another website 1 Determine how users interact with data 1 Control how data displays in web browsers
Important Security is increasingly important when you publish data on the web. Review the security guidelines in the FileMaker Security Guide, located in the Electronic Documentation folder (inside the English Extras folder).
FileMaker Instant Web Publishing Guide
Data from a FileMaker layout displayed in a web browser with Instant Web Publishing
Data displayed in a FileMaker Pro layout

About this guide

This guide provides information about the Instant Web Publishing and static web publishing features in FileMaker Pro. It explains:
what you need to publish databases on the web how to publish your databases using FileMaker Pro Instant Web Publishing what web users need to access databases how web users can access and interact with your database on the Internet or an intranet
FileMaker Pro documentation uses the term publishing on the web to refer to databases that users can access on the Internet or on an intranet using a web browser. This guide uses FileMaker Pro to refer to both FileMaker Pro and FileMaker Developer, unless describing specific FileMaker Developer features.
Important You can download PDFs of FileMaker 7 documentation from www.filemaker.com/ downloads. Any updates to this document are also available from the website.
Web publishing requirements
To publish databases using Instant Web Publishing you need:
1 a Windows- or Mac OS-based computer running FileMaker Pro or FileMaker Server Advanced,
enabled for Instant Web Publishing
Note Instant Web Publishing is not supported in the basic FileMaker Server product.
1 access to the Internet or an intranet 1 one or more open FileMaker Pro databases
1 the FileMaker Pro web publishing components (automatically installed with a complete

installation)

1 Windows: To test your database for web browser access, you must have Internet Explorer by
Microsoft, version 6.0 in Windows 98, Windows NT 4.0 with Service Pack 6a (SP6a) and higher, Windows 2000, Windows XP.
1 Mac OS X: To test your database for web browser access, use Microsoft Internet Explorer version
5.1 and 5.2 on Mac OS X 10.2.8 or Safari 1.1 on Mac OS X 10.3.
Connecting to the Internet or an intranet
When you publish databases on the Internet or an intranet, the host computer must be running FileMaker Pro or FileMaker Server Advanced, and the databases you want to share must be open. In addition:
1 It is strongly recommended that you publish your database on a computer with a full-time Internet
or intranet connection using TCP/IP. You can publish databases without a full-time connection, but they are only available to users when your computer is connected to the Internet or an intranet.

1 The host computer should have a dedicated static (permanent) IP address or a domain name. If
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

functionality web users need to interact with your databases on the web.
1 Find mode allows more flexible and powerful searchesweb users can now perform multiple
find requests, omit search criteria, and extend (broaden) or constrain (narrow) existing find requests.
1 When web users connect, individual multi-threaded sessions are maintained. Like web
applications, their transactions are remembered across multiple screens. To the host machine, there is no difference between a session started from a web client or a FileMaker Pro client. This means that some tasks performed by web users, such as creating found sets, setting global variables, and sorting and navigating records no longer affect the database on the host computer or other web users. For more information on new FileMaker 7 features, including Instant Web Publishing features, see the Installation and New Features Guide for FileMaker Pro and FileMaker Developer.
Publishing files from previous versions of FileMaker Pro
Before updating existing databases to FileMaker Pro 7, it is important to review the Converting FileMaker Databases from Previous Versions guide, located in the Electronic Documentation folder (inside the English Extras folder). Here are some considerations when converting files that are shared with Instant Web Publishing:
1 You are no longer limited to picking a couple of layouts for web viewsnow, all layouts are
available to web users, based on their user accounts. The Web Styles available with FileMaker Pro 6 and earlier are no longer supported. After you convert your files, re-evaluate which layouts should be available on the web to each user account.
1 The access privileges model has been improved. Consider re-assigning user names and passwords
to take advantage of the integrated security model. For more information on accounts and privileges, see FileMaker Pro Help.
1 Script support for the web has been enhanced. 1 Access privileges for web users can be set to allow execution of specific, individual scripts and

Sharing a database with Instant Web Publishing
To publish databases on the web with FileMaker Pro, you enable the Instant Web Publishing feature, then determine which user accounts can access each database from a web browser: To enable Instant Web Publishing:
1. Open the database. 2. Open the Instant Web Publishing dialog box and enable Instant Web Publishing.
1 Windows: choose Edit menu > Sharing > Instant Web Publishing. 1 Mac OS X: choose FileMaker Pro menu > Sharing > Instant Web Publishing.
Enable Instant Web Publishing
View the IP address Choose a language for the status area and Help file Specify which users can access a published database
Specify port number, enable log files, set time out, and more Choose a file to share on the web
Suppress filenames in the Database Homepage FileMaker Pro Instant Web Publishing dialog box
3. Select the filename to publish on the web from the list of open files.
4. Choose which users can access the file.
Choose this To provide access to these users

All users

Anyone who has the IP address or domain name of your computer hosting the database. If the Guest account is enabled and has the Instant Web Publishing privilege set enabled, web users open the database without being prompted for an account name and password when opening files. Allows select users access to the database. Users must enter their account name and password defined in Accounts and Privileges. This default setting prevents any user from accessing the database with Instant Web Publishing.
Specify users by privilege set No users
1 The FileMaker Pro Log in using <account name> feature in the File Options dialog box does not
work when accessing files from the web.
1 Web users can open databases without specifying a password by logging in with the Guest
account. See Logging into a file on page 18 and FileMaker Pro Help for information on enabling the Guest account for Instant Web Publishing.
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:
1. Open the Instant Web Publishing dialog box. 2. For Advanced Options, click Specify, then type the desired TCP/IP port number. 3. Click OK, then OK to save the changes.
Specify the port number View the maximum number of connections
Allow access to specified IP addresses

Enable log files

Specify time out for inactive accounts
FileMaker Pro Advanced Web Publishing Options dialog box
Important If you use a port number other than 80, web users cannot access your database unless they append a colon, and the new port number, to your IP address (or domain name). For example, users would type 12.34.56.78:591 or http://accounts.yourcompany.com:591 in a web browser. Or you can provide access to the database from a link that contains the IP address and port number. For more information, see Linking to a database from an HTML page on page 15.

or close web published databases, or if you are hosting the databases with a dynamic IP address, you must update your HTML links.
1 The URL syntax for linking to a particular database is different than FileMaker Pro 6 and earlier,
so you must update the link after converting the file.
1 If youre hosting files with FileMaker Pro, you can store the static HTML pages and any
accompanying images in the Web folder inside the FileMaker Pro folder.
Publishing FileMaker Pro data on static web pages
With Instant Web Publishing, data is updated in a web browser window each time the browser requests data from FileMaker Pro. This is called dynamic publishing. With static publishing, the data you publish from FileMaker Pro doesnt change with each new request. Static publishing might be a good option for you if:
1 your data doesnt change often. 1 you dont have full-time internet access. 1 you dont want users to connect directly to your database.
To publish static data, you need:
1 a web site hosted on a web server (you can enable Instant Web Publishing to have FileMaker Pro
be the web server for items in the FileMaker Pro Web folder).
1 FileMaker Pro, and one or more databases with data
1 a computer connected to the Internet or an intranet (you only need to connect when you upload
your web page to a web server)
1 an application for copying (uploading) files to your web server application 1 a text-editing or web-authoring application (optional) General steps for publishing static data
With static publishing, you export data to a web page, then add the web page to your existing web site. Web users connect to your web site, not to your database. To publish static data from FileMaker Pro:
1. Find the appropriate records, then choose File menu > Export Records, and choose HTML Table

or XML.

1 Choose HTML Table to generate a table of data that can be viewed by supported web browsers.
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 The default privilege set for Guest accounts provides read-only access. You can change the
default privilege in Extended Privileges. For more information, see FileMaker Pro Help.
1 Web users generally cannot modify their account password from a web browser. It is possible,
however, to build this functionality into your database with the Change Password script step (to enable web users to change their password).
1 With FileMaker Server Advanced, you can enable an additional log in screen that does not
display filenames in the Database Homepage unless web users have an account name and password that provides access to the file.
Working with data in Instant Web Publishing
In FileMaker Pro, the Instant Web Publishing status area has been redesigned to resemble the desktop application. Web users interact with databases on the web in Browse or Find mode. All the features that enable web users to interact with your database, for example, entering, editing, deleting, and finding records, are accessible from the status area.
Viewing and modifying records in Browse mode

they are stacked in a layout, with objects at the background of a layout being rendered before objects in the foreground. Use this to determine the tab order by stacking objects on the layout in the order you want users to tab into them.
1 Pop-up menus and pop-up lists display as HTML pop-up menus. Web users can't edit value lists
by using an Edit item, or enter values that aren't in a value list by using an Other item.
1 If your solution includes multiple files, Instant Web Publishing must be enabled in all databases.
If you dont want related files to be accessed directly, you can exclude a filename from the Database Homepage by enabling the Dont display in the Instant Web Publishing Database Homepage option in the Sharing dialog box.
1 If your layout contains a portal, related records also display in a web browser within a portal,
provided that the related file or table is also shared with Instant Web Publishing. When you submit a record containing a portal you might be notified that another user has modified one of the records since you loaded the page. If this occurs, refresh your page and submit the data again. If this is a likely scenario, consider using portals as read only forms. Alternatively, you can edit related record data in portals by using the Go To Related Record script step and editing them directly.
1 Web users can create and edit portal records. To delete a portal record, you must provide a
scripted button that selects the appropriate portal record, then deletes it.
General database design considerations
Keep the following points in mind:
1 If you are designing a database that will be accessed by both Instant Web Publishing and
FileMaker Pro network clients, its best to design with web clients in mind to ensure compatibility across both technologies.
1 Communication from a client to the FileMaker host goes through intermediary technologies with
Instant Web Publishing. When you request data with Instant Web Publishing, you are sending the request from a web browser to a virtual FileMaker environment, which processes your request, then requests and retrieves the results from FileMaker Pro. These results are then passed back to the browser. This interaction is usually undetectable to web users, but occasionally you must take action to make sure the results are the same regardless of how clients access your database. Because web users dont have a direct connection to the host, they arent notified immediately when data changes. For example, you may need to update your scripts to include the Commit Record/Request to refresh the browser window. For more information, see Script steps tips and considerations on page 27 and Creating a script to log out of a database and close the session on page 29.

1 When defining account names and passwords, use characters included in the ISO Latin-1
character set (except colons). To avoid characters that may be interpreted incorrectly on the web, you may want to limit account names and passwords to alphabetic and numeric characters only.
1 It is best not to set too many field validations on a layout. When web users submit a record, an
error is returned each time a validation has not been met.
1 Typically, third party plug-ins can be used for web published databases if they do not attempt to
display information to an end-users screen, if they do not require direct end-user interaction, if they do not interact with the FileMaker Pro user interface, or otherwise require interaction from end users.
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.

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 the FileMaker Server Advanced Web Publishing Installation Guide, included with FileMaker Server Advanced.
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 information about the following information in your documentation:
1 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.
1 Navigating the database: Instruct web users on how to view records in appropriate layouts and

layout views.

1 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 21.
Chapter 5 Testing, monitoring, and securing your site
Before notifying users that your published database is available, it is important to verify that it looks and functions as you expect.
1 Test features like finding, adding, deleting, and sorting records with different accounts and

privilege sets.

1 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.
1 Click all scripted buttons to verify that the outcome is expected. See Scripts and Instant Web
Publishing on page 27 for information on designing web-friendly scripts.

Integrate your database with another website Determine how users interact with data Control how data displays in web browsers
For more information, see FileMaker Server Custom Web Publishing with XML and XSLT and FileMaker Server Custom Web Publishing with PHP. Important Security is increasingly important when you publish data on the web. Review the security guidelines in the FileMaker Pro Users Guide, available as a PDF file from www.filemaker.com/downloads.
Data from a FileMaker layout displayed in a web browser with Instant Web Publishing
Data displayed in a FileMaker Pro layout

About this guide

This guide provides information about the Instant Web Publishing and static web publishing features in FileMaker Pro. It explains:
what you need to publish databases on the web how to publish your databases using FileMaker Instant Web Publishing what web users need to access databases how web users can access and interact with your database on the internet or an intranet
FileMaker Pro documentation uses the term publishing on the web to refer to databases that users can access on the internet or on an intranet using a web browser. This guide uses FileMaker Pro to refer to both FileMaker Pro and FileMaker Pro Advanced, unless describing specific FileMaker Pro Advanced features. Important You can download PDFs of FileMaker documentation from www.filemaker.com/downloads. Any updates to this document are also available from the website.

Chapter 1

About publishing FileMaker Pro databases on the web
Instant Web Publishing requirements
To publish databases using Instant Web Publishing you need:
a Windows- or Mac OS-based computer running FileMaker Pro or FileMaker Server Advanced, enabled for Instant Web Publishing access to the internet or an intranet one or more open FileMaker Pro databases the FileMaker Pro web publishing components (automatically installed with a complete installation) a web browser for testing database access (see Web browser requirements on page 19)
Important You cannot enable Instant Web Publishing in FileMaker Pro if FileMaker Server or FileMaker Server Advanced is also running on the same computer.

Connecting to the internet or an intranet
When you publish databases on the internet or an intranet, the host computer must be running FileMaker Pro or FileMaker Server Advanced, and the databases you want to share must be open. In addition:
It is strongly recommended that you publish your database on a computer with a full-time internet or intranet connection using TCP/IP. You can publish databases without a full-time connection, but they are only available to users when your computer is connected to the internet or an intranet. The host computer should have a dedicated static (permanent) IP address or a domain name. If 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. Note You must use FileMaker Server Advanced to use Instant Web Publishing to share files with more than five 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. 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 36. For more information, see FileMaker Server Custom Web Publishing with XML and XSLT, FileMaker Server Custom Web Publishing with PHP and FileMaker Server Help.
Web publishing improvements
Web viewers work in Instant Web Publishing. These objects can calculate a URL based on field data and display the web page directly in a FileMaker Pro layout. For more information about web viewers, see www.filemaker.com/support/technologies. For information on other new FileMaker Pro and FileMaker Pro Advanced features, see the Installation and New Features Guide for FileMaker Pro and FileMaker Pro Advanced.
Publishing files from previous versions of FileMaker Pro
Publishing files from FileMaker Pro 7 and 8
Because FileMaker Pro, versions 7, 8, 8.5, and 9, share the same format, Filemaker Pro 9 can open FileMaker Pro 7 and 8 files without converting them. You can even use FileMaker Pro 9 files with FileMaker Pro 7 and 8. However, any layout that contains new features will not be supported in Instant Web Publishing when you open the file in a previous version. FileMaker recommends that, once you have created or opened a file in FileMaker Pro 9, you do not make database design or layout changes using an earlier version of FileMaker Pro, particularly to features that have changed in FileMaker Pro 9.

Chapter 2

Publishing your database on the web
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:
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 type the desired TCP/IP port number. 3. Click OK, then OK to save the changes.
Specify the port number View the maximum number of connections
Allow access to specified IP addresses

Enable log files

Specify time out for inactive accounts
Advanced Web Publishing Options dialog box
Important If you use a port number other than 80, web users cannot access your database unless they append a colon, and the new port number, to your IP address (or domain name). For example, users would type 12.34.56.78:591 or http://accounts.yourcompany.com:591 in a web browser. Or you can provide access to the database from a link that contains the IP address and port number. For more information, see Linking to a database from an HTML page on page 15.
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.

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. 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 36 and Logging out of a database and closing a web session on page 24 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 or a homepage you create
If the database is hosted with FileMaker Pro or FileMaker Pro Advanced:
http://<IP address>:<Port number>
If the database is hosted with FileMaker Server Advanced:
http://<IP address>:<Port number>/fmi/iwp/

A particular database

http://<IP address>:<Port number>/fmi/iwp/ cgi?-db=<database name>&-loadframes
Keep these points in mind:
If you close your files frequently, or if web users access a number of databases, consider linking to the Database Homepage, which dynamically creates links for all databases that are open and shared with Instant Web Publishing. For more information on the Database Homepage, see Accessing a FileMaker database from the web on page 20. The link you provide can access a database and show the default layout. If additional functionality is desired, consider including a startup script in the database that automates the desired tasks. If possible, host the databases on a static IP address or use a domain name. In some environments, a new IP address is assigned dynamically to a computer every time it reconnects to the network. The URL syntax for linking to a particular database is different than FileMaker Pro 6 and earlier, so you must update the link after converting the file. If youre hosting files with FileMaker Pro, you can store the static HTML pages and any accompanying images in the Web folder inside the FileMaker Pro folder.

Using a custom home page

To replace the default Database Homepage, place an HTML file named iwp_home.html in the Web folder inside the FileMaker Pro folder. Web users are returned to this page when they log out of a session or the session times out. Note If you are hosting databases with FileMaker Server Advanced, place the custom home page in the Web Publishing/IWP folder where FileMaker Server is installed (Windows) or in the /Library/FileMaker Server/Web Publishing/IWP folder (Mac OS). You can use the iwp_home.html file that is on your product CD as a basis for your custom home page. Be sure to make a copy of the original file before modifying it. Or you can create your own home page, such as one that redirects web users to another page on your web site. If there is no file named iwp_home.html in the Web folder (FileMaker Pro, FileMaker Pro Advanced) or the iwp folder (FileMaker Server Advanced), Instant Web Publishing uses the default Database Homepage. In order to prevent a custom home page from loading into the Instant Web Publishing layout frame when a user logs out via a script or a session times out, the following JavaScript should be added to the head section of the iwp_home.html file:

Important Manage 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:

a web browser.

On Windows Vista, Windows XP, Windows Server 2003, or Windows 2000 Server, use On Mac OS X, use
Internet Explorer 6.0 and 7.0 Firefox 2.0
Safari 1.2, 1.3 (Mac OS X 10.3), Safari 2.0 (Mac OS X 10.4) Firefox 2.0
Note These requirements may differ from those of the FileMaker product that hosts the database.
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
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. 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. 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. If you dont see an open, shared database listed:
Check its filename: it should be unique and not contain single or double quotation marks. Be sure Dont display in Instant Web Publishing homepage in the Instant Web Publishing dialog box is cleared.
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

Chapter 3

Working with FileMaker databases on the web

Logging in to a file

When opening a database, web users may be prompted for their account information.

Forms-based login page

If the Guest account is enabled with the Instant Web Publishing extended privilege, web users have the option to log in with the Guest account instead of an account name and password. If the Guest account is the only account with the Instant Web Publishing extended privilege enabled, web users automatically log in with the Guest account, and they do not see the login page. The default privilege set for Guest accounts provides read-only access. You can change the default privilege in the Accounts tab of the Manage Accounts & Privileges dialog box. For more information, see FileMaker Pro Help. Web users generally cannot modify their account password from a web browser. However, it is possible to use the Change Password script step to designate a preset password that the user can change to. You can let users change their login accounts from a web browser with the Re-Login script step (for example, to switch from the Guest account to an account with more privileges). Since basic authentication has been replaced with a forms-based model, account names and passwords are not restricted to the ISO-Latin-1 character set. With FileMaker Server Advanced, you can limit the list of hosted databases displayed in the Database Homepage to only those databases each web user can access. If this option is selected, web users will be prompted for their account information before they view the Database Homepage.

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.

Only the Tab key is supported for navigating between fields or objects in Instant Web Publishing. Pop-up menus and pop-up lists display as HTML pop-up menus. Web users cant edit value lists by using an Edit item, or enter values that arent in a value list by using an Other item.

Chapter 4

Designing a database for Instant Web Publishing
If your solution includes multiple files, Instant Web Publishing must be enabled in all databases. If you dont want related files to be accessed directly, you can exclude a filename from the Database Homepage by enabling the Dont display in the Instant Web Publishing Database Homepage option in the Instant Web Publishing dialog box. If your solution includes multiple files, then identical accounts, passwords, and privilege sets must be created in each file used by Instant Web Publishing. The account and password you provide when you open the first file is used to authenticate related files. If your layout contains a portal, related records also display in a web browser within a portal, provided that the related file or table is also shared with Instant Web Publishing. When you submit a record containing a portal you might be notified that another user has modified one of the records since you loaded the page. If this occurs, refresh your page and submit the data again. If this is a likely scenario, consider using portals as read only forms. Alternatively, you can edit related record data in portals by using the Go To Related Record script step and editing them directly. Web users can create and edit portal records. To delete a portal record, you must provide a scripted button that selects the appropriate portal record, then deletes it.
General database design considerations
Keep the following points in mind:
If you are designing a database that will be accessed by both Instant Web Publishing and FileMaker Pro network clients, its best to design with web clients in mind to ensure compatibility across both technologies. Communication from a client to the FileMaker host goes through intermediary technologies with Instant Web Publishing. When you request data with Instant Web Publishing, you are sending the request from a web browser to a virtual FileMaker environment, which processes your request, then requests and retrieves the results from FileMaker Pro. These results are then passed back to the browser. This interaction is usually undetectable to web users, but occasionally you must take action to make sure the results are the same regardless of how clients access your database. Because web users dont have a direct connection to the host, they arent notified immediately when data changes. For example, you may need to update your scripts to include the Commit Records/Requests script step to refresh the browser window. For more information, see Script steps tips and considerations on page 33 and Creating a script to log out of a database and close the session on page 36. Each database must be assigned a unique filename, when you host them with Instant Web Publishing. If you have two hosted databases with the same name, only one appears in the Database Homepage in Instant Web Publishing. When defining account names and passwords, avoid characters that may be interpreted incorrectly on the web. You may want to limit account names and passwords to alphabetic and numeric characters only. It is best not to set too many field validations on a layout. When web users submit a record, an error is returned each time a validation has not been met. Typically, third party plug-ins can be used for web published databases if they do not attempt to display information to an end-users screen, if they do not require direct end-user interaction, if they do not interact with the FileMaker Pro user interface, or otherwise require interaction from end users.

Indicate script steps that are 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:
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. Alerts are not displayed in the web browser for errors encountered in scripts that are run from Instant Web Publishing. Errors are recorded in the application.log file, (located in the FileMaker Pro/Web logs folder) if Script errors logging is enabled. See Monitoring web activity with log files on page 37. See information for Set Error Capture in Script Steps on page 35. 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. 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.
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.
If the Allow User Abort script step option is enabled (On), unsupported script steps will stop the script from continuing. If the Allow User Abort script step is set to Off, (default), unsupported script steps are skipped over and the script continues to execute. If this script step is not included, scripts are executed as if the feature is enabled, so unsupported script steps will stop scripts.
Some scripts that work with one step from a FileMaker Pro client may require an additional Commit Records/Requests 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. Similarly, any script that modifies data should include the Commit Records/Requests step, because all data changes arent visible in the browser until the data is saved, or submitted to the server. This includes script steps such as Insert Text, Insert Calculated Result, Insert from Last Visited, Insert Current Date, Insert Current Time, Cut, Insert Copy, Copy Record/Request, Copy All Records/Requests, and Paste. Many single-step buttons should be converted into scripted buttons to include the Commit Records/Requests step. When you design scripts that are executed from a web browser, its a good idea to include the Commit Records/Requests step at the end of a script to make sure all changes are saved. To create conditional scripts based on the type of client, use the Get(ApplicationVersion) function. If the value returned includes FileMaker 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. 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 on page 36. 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. In Instant Web Publishing, the GetLayoutObjectAttribute function works as in FileMaker Pro, except for the following differences:

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.

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

Browse mode capabilities 22 Instant Web Publishing 22 browser, web open database URL 15 publishing requirements 7 requirements 19 viewing databases in 19 buttons 28
enabling Instant Web Publishing 7, 11, 19 Enter Browse Mode script step 30 Exit Application script step 35, 36 External functions, for Web publishing 38 external SQL data sources 30
Cascading Style Sheets (CSS) 27 limitations 27 changing settings 12 character set restrictions, account names and passwords 21, 29 Close Window script step 35 Commit Records/Requests script step 29, 34, 35 container fields, restrictions 30 converting files from previous versions 8 custom environments creating 31 documentation 25 custom home pages 16
FileMaker Pro converting files from previous versions 8 differences with Instant Web Publishing 25 hosting databases 7 Instant Web Publishing 11 maximum number of web connections 14 publishing files from previous versions 8 publishing static web pages 16 setting starting layout 30 web access requirements 20 FileMaker Pro Advanced custom menus 30 tooltips 26 FileMaker Pro databases, accessing from the web 19
FileMaker Pro layouts designing for Instant Web Publishing 27 using portals 29 FileMaker Server Advanced Custom Web Publishing 5 filtering databases 21 hosting databases 7, 24 security 24 using plug-ins 30 filenames, suppressing in Database Homepage 29 Find mode capabilities 23 constrain found set 23 extend found set 23 Instant Web Publishing 23
GetLayoutObjectAttribute function 34 Go to Field script step 35 Go to Layout script step 30 Go to Object script step 30 Go to Related Record script step 29 Guest account disabling 21 enabling 21 with Instant Web Publishing 12, 21
Help, Instant Web Publishing 22 hide status area about 25, 31 on startup 24 toggle 24 Homepage See Database Homepage hosting databases with FileMaker Pro 7 with FileMaker Server Advanced 7
Instant Web Publishing about 5 accessing records 22 Apache 36 automating with scripts 33 Browse mode 22 changing settings 12 choosing a language 13 custom home page 16 designing databases 27 differences with FileMaker Pro 25 Drop-down Calendar field format 30 enabling 7, 11, 19 FileMaker Pro layouts 27 Find mode 23 Guest account 21 hiding status area 31 hosting with FileMaker Server Advanced 36 IIS 36 Mac OS X requirements 7 new features 8 script steps, differences with FileMaker Pro 35 specifying port number 13 specifying sort order 31 using dynamic IP address 7 using static IP address 7 viewing browser pages 19 web user access 12 Windows requirements 7 IP address appending port number 20 dynamic 7 restricting access 14 static 7, 15 typing in browser 20 ISO-Latin-1 character set 21 ISP 7

language, choosing for Instant Web Publishing 13 layout view limiting access 8 toggling 8 layouts 8 layouts, limiting with accounts and privileges 27 List View designing for 28 differences with FileMaker 28
idle session, disconnecting 15 IIS, hosting Instant Web Publishing databases 36
log files archiving 38 creating 37 logging options 38 monitoring web activity 37 securing 38 Log Out button 24 importance 24 script 36 login page 21
Refresh Window script step 35 Re-Login script step 21, 35 requirements web browser 19 web publishing 7 restricting access to databases 14 RTF (rich text formatting) 26
scripts See also script steps by name Accounts and Privileges 33 behavior in Instant Web Publishing 35 log out 36 testing 37 tips and considerations 33 using in Instant Web Publishing 33 security Accounts and Privileges 8 considerations 38 data access 38 document and data storage 39 FileMaker Server Advanced 7 guidelines 5 restricting web access 14 reviewing script steps 39 SSL encryption 7 with multiple accounts 38 with static web pages 17 Select Window script step 35 session, logging out 24 Set Error Capture script step 8, 35 Set Web Viewer script step 32, 35 Show/Hide Status Area script step 31 sort order, specifying 31 Sort script step 35 SQL data sources, external 30 SSL encryption 7, 24 static IP address 15 static publishing 16 status area changing language in 13 hiding 25, 31 Submit button 22
Mac OS X port number 14 web browser requirements 19 web publishing requirements 7 maximum number of web connections, FileMaker Pro 14 monitoring web activity 37
network clients, database design 29 New Window script step 35
ODBC data sources 30 OLE 26 limitations 30 Open URL script step 35
pages, web, viewing databases in 19 passwords no login password 21 with multiple accounts 38 Pause/Resume Script script step 35 Perform Script script step 35 port number appending to IP address 20 changing 13 configuring 20 Mac OS X 14 specifying for web publishing 13 publishing databases connecting to Internet or intranet 7 from previous versions of FileMaker Pro 8 with Instant Web Publishing 11

tab order 28

tab panels 28, 30 Table View designing for 28 differences with FileMaker 28 restrictions 9 setting properties 28 TCP/IP port number 13 testing your published database 37 third party plug-ins 29 with FileMaker Server Advanced 30 time out setting 15, 24 tooltips, FileMaker Pro Advanced 26
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