creat a mobile website

Preparing a database for mobile web access Before using PHP Site Assistant, there are some things that should be done within the database. Taking these steps now saves time and improves site performance. • Designate layouts that will only be accessed by web-based users, and not FileMaker Pro users. When FileMaker data is requested from a web browser, the layout must also be included in the request. FileMaker sends data from every field on that specified layout to the web publishing engine, then on to the PHP application on the web server. It is important that the layout web users are interacting with only contains fields that are critical to the mobile users. This eliminates unnecessary overhead on the web server. • Before running PHP Site Assistant, format the fields on your designated web layouts to display the same way they will on a web page. For example, first format a Gender field to display radio buttons with the “Male” and “Female” choices on the FileMaker layout. When PHP Site Assistant generates the site, it automatically creates the appropriate HTML to display the field the same way. Use pop-up menus and radio buttons wherever appropriate to make data entry easier for users. • Because the FileMaker API for PHP also targets a specific FileMaker layout when searching a database, it is important to restrict the number of users who can modify these layouts. If a field is unknowingly removed from a layout, the webbased search could produce unexpected results. • Create separate accounts and privilege sets for web-based access. This privilege set should only provide access to those layouts designated for webbased users. Similarly, the Extended Privileges should only allow access via PHP web publishing. Restricting ways that web-based users can access your databases reduces your security risks. • Whether users are accessing data using FileMaker Pro or a web browser, performance will always be better if the fields you’re working with are indexed. Wherever possible make sure that sorts and finds are not being performed on fields where indexing is turned off or that use or reference unstored