FileMaker Pro vs Access Update

I am working on a second tutorial for the eBook I am writing about using spreadsheets and databases for data analysis.  The FileMaker Pro database I have created has only two tables and four layouts, but it is over 500 MB in file size.  The comparisons I have thus far are:

• Access allows you to easily format text as zip codes and phone numbers, but FileMaker Pro does not
• Access allows you to do a Compact and Repair, but FileMaker does not have that feature in the menu
• Creating a button to open a URL was very easy with FileMaker
• Creating list features with Value Lists in FileMaker is child's play - so easy!
• FileMaker Pro works on the Mac and Windows computers and provides a 30-day free preview, but Access works only on Windows computers
• After you create a database with FileMaker Pro, you can sync it to your iPad or iPhone FileMake Go app.  Once it is synced, you can edit the database and enter data (a real plus!).  FileMaker Pro has settings for themes that work best on the iPad and iPhone.
• Calculating an age is more complex calculation in FileMaker (although may be more accurate) than using Access.
• If/then and other mathematical calculations are basically the same in both database software packages.

Microsoft Access 2010 or Apple Filemaker Pro 12?

I have used and taught others to use Microsoft Access for the past 15 years but must consider changing to Apple Filemaker Pro.  Why? -- because Filemaker Pro is available for both the Mac and the PC.  Furthermore, Filemaker Go is a free app for the iPad.  Finally, Filemaker Pro is must easier to use than Access!

The only plus for Microsoft Access is the cost.  Microsoft Access is one of seven apps available from Office University 2010 for $99.99.  The academic version of Filemaker Pro costs $179.

I am teaching an informatics course this summer and discovered that 1/3 of the students are Mac users.  What it means is that I cannot use the lessons I developed on relational databases using Access 2010.  As a result, I spent time over the last couple of weekends working through the Filemaker Pro tutorial to learn how to use the software.

Although Microsoft Access 2010 is a great improvement over earlier versions, it is still clunky and not intuitive for learners.  There are essentially four different views - tables, queries, forms, and reports.  In contrast, Filemaker Pro allows the user to do the same functions using different "Layouts."

Filemaker Pro is available as a 30 day preview, so I can incorporate it into the course without additional fees for the students.

My next step is to import the tables for the Metabolic Syndrome database I created from Access into Filemaker Pro.  That process should help shed new insight on the differences between the two applications.

Learning Access 2010

I worked with a student yesterday on a synthesis project.  She asked me to consider writing a textbook on Access.  I wish I had the time.  It is so difficult to use textbooks that do not have healthcare examples.  It is so difficult for clinicians to see the relevance to their practice without concrete examples.  This morning I researched for resources that I could use in conjunction with data sets such as those from the Centers for Disease Control and Prevention (CDC).  I found a great resource in GCF Learning!!   It includes concise lessons on Access 2010.  Each of the four categories shown below have instructional videos.  The tutorial also includes a sample Access file that users can download.  The tutorial can be accessed from http://www.gcflearnfree.org/access2010

Access Basics

• 1: Introduction to Databases
• 2: Introduction to Objects
• 3: Getting Started in Access
• 4: Managing Databases and Objects

Working With Data

• 5: Working with Tables
• 6: Working with Forms
• 7: Sorting and Filtering Records

Running Queries and Reports

• 8: Designing a Query
• 9: More Query Design Options
• 10: Creating Reports
• 11: Advanced Report Options

Database Design Tips

• 12: Modifying Tables
• 13: Creating Forms
• 14: Formatting Forms
• 15: Designing Your Own Database