Considerations for "Webifying" a FileMaker Database
- Proper file names now will allow for future database web publishing.
- Field naming considerations for databases that are shared, published to the web, and/or using ODBC.
- Field names should not contain slash, dash, asterisk, or spaces.
- Consider field labels that are more descriptive and understandable.
- Developers use value lists to guide the user's entry while protecting the accuracy of their data.
- Format fields to tie the field name, user interface, and value list together.
- Creating passwords and setting privileges grants user access and controls what others can do to your data.
- Encourage accuracy by choosing the appropriate user interface.
File Naming Considerations — Proper file names now will allow for future database web publishing.
- Use all lower case letters, and underscore rather than spaces for file names, layouts, and fields.
- Limit database filenames to 8 characters.
- File names for databases not intended to use FileMaker's Instant Web Publishing feature, should end the file name with an underscore character.
Field naming considerations for databases that are shared, published to the web, and/or using ODBC.
- Good database design suggests the use of field names that do not contain spaces. This is a practice worth learning in order to avoid problems that are often experienced when publishing to the Web or using ODBC. Instead use an underscore character (e.g. Student_ID).
- Field names can be as simple as 'q1' to indicate 'question 1'.
- The naming method you choose to use needs to make sense to others. There should be no question as to the meaning of the field name (an abbreviated field name such as 'MBR' could stand for 'Master Bedroom' or 'member'; 'ST' could stand for 'Street' or 'Saint').
Field names should not contain characters such as a slash, dash, or an asterisk....
When FileMaker performs calculations utilizing field names containing chararcters such as slash, dash, or an asterisk, it attempts to perform the mathematical function associated with that character by dividing, subtracting, or multiplying (respectively). It is also a good practice to refrain from using spaces in field names.
Consider field labels that are more descriptive and understandable.
When defining a field, a layout containing a more descriptive, text field label (e.g. 'lastname') can be easier to use and understand than a label containing the field name (such as 'q1', representing 'question1').
| Figure 1.1 Field label defaults to the field name. |
![]() |
| Figure 1.2 Field label renamed to a more descriptive name. |
![]() |
Developers use value lists to guide the user's entry while protecting the accuracy of their data.
Consider a Value List Name that matches the Field Name (or the Field Label) of the field that will use it. Value Lists are customizable lists that populate a field, based on user selection, with text contained in the list. Radio buttons and check boxes make use of value lists.
![]() |
| Figure 2.1 A pop-up menu is selected as the user interface for the 'q3' field. The values for the pop-up menu will be drawn from the 'q3' value list. A pop-up menu presents the user with a list of values to choose from but does not allow the user to enter their own data or to edit this list. |
Format Fields to tie the field name, user interface, and value list together.
Select style, value list, and behavior to use for each field. To do so, select Layout View > Format > Field Format. Field Formatting is done once the field has been defined and a value list has been defined. For example, this step tells the 'q3' (example has a field label called 'Course Name') field to use a 'pop-up menu' interface and pull the values from a 'value list' named 'q3'.
![]() |
| Figure 3.1 Database developers often use matching Field Names and Value List Names (e.g. 'q3'). |
Creating passwords and setting privileges grants user access and controls what others can do to your data.
Select File > Access Privileges> Passwords > Click Done when finished.
![]() |
| Figure 4.1 Data can be protected by setting access privileges and creating passwords. |
Encourage users to enter complete, and accurate, information by choosing the appropriate user interface.
Fields can be displayed by using pop-up lists, pop-up menus, radio buttons, and check boxes. To best determine the best interface, consider whether you wish to....
- allow the user to type in their own data (editable list). This is referred to as a Pop-up List.
- present the user with a set of choices to pick from (un-editable list). This is referred to as a Pop-up Menu.
- provide the user a single selection from a permanently displayed set of values. These are referred to as Radio Buttons.
- allow the user to make multiple selections from a permanently displayed set of values. These are referred to as Check Boxes.
![]() |
| Figure 5.1 Select the appropriate user interface from the Format menu > Field Format selection. |
![]() |
| Figure 5.2 Field Format may be selected by clicking on the field name with the right mouse button (PC/Windows platform only). |
NOTE: If you intend to do sorting and/or reporting with your data, be sure to test the effect of your user interface choice.






