FileMaker and Departmental Database Applications

 

 

FileMaker Pro is widely used throughout the MIT community for many reasons. For data management needs that exceed what a spreadsheet can offer, FileMaker provides great flexibility, an intuitive interface, and a shallow learning curve for basic database development. Add a site license and it's no surprise that thousands of FileMaker databases proliferate throughout MIT departments, labs, and centers. They range from simple single table files, used mostly for sorting and searching, all the way to complex applications with dozens of related tables and sophisticated functionalities.

FileMaker's ease of use and rapid development environment makes it an understandable answer to database needs, though not always the right answer. However, it can be the right answer in many situations, when the right design and infrastructure is implemented. This section provides guidelines for proper implementation of FileMaker database applications in the MIT environment.

When to Develop and Deploy a FileMaker Application

How do you know if FileMaker is the right answer to your needs? If your database needs fit within these constraints, developing a FileMaker application is appropriate:

  • The database does not house any combination of personal information as defined in section 17.02 of the Massachusetts regulation for safeguarding the personal information of Massachusetts residents. This includes a person's name in combination with ANY of the following:
    • Social Security Number
    • Driver's license or state ID number
    • Financial account or credit card number
  • The database is not a system of record
  • The database will not share sensitive information via the web
  • If web-enabled, the volume of activity will not exceed 80 simultaneous connections
  • The database will be accessed through FileMaker clients from a single department, lab, or center

 

If the statements listed above are True, then FileMaker may be suitable for your needs. When implemented according to MIT standards and best practices, FileMaker should serve your department well. And by applying ITAG's standards to your FileMaker implementation, you can be assured that you are doing your best to protect your department's valuable data.

This web site addresses how FileMaker can meet ITAG's standards. Each of the topics in this section corresponds to a particular ITAG standard and provides guidance on how you can make your FileMaker implementation comply to its best capability.

In addition to the in-depth information contained within this site, you are also strongly urged to refer to this handy checklist of security guidelines.

When FileMaker is Not the Answer

If your needs exceed the limits listed above, you should probably be looking at another technology. DCAD can help you make that judgment call and provide you with the necessary services to get you on your way.

Back To Top