I know this response is a little late, but as someone who has used both FileMaker and Access extensively I would like to clarify a few things for you. First, they are both databases. That's where the similarity stops. They really are different. Here's how: (1) Access has an ANSI SQL-compliant query interface, FileMaker doesn't. (2) FileMaker uses a flat-file data structure. (3) Access comes with a rich programming environment and the ability to make sophisticated forms for doing real work. This is a big one. My last big project was 70k lines of VBA code that scraped data and modeled an airplane electrical system. My previous team built a suite of apps that was nearly 1M lines. VBA isn't object-oriented because its class entities lack inheritance, but you can fake a lot using interfaces. FileMaker can be fiddled with using AppleScript and has some simple interface components, but that's it. You can create applications with Access and separate the executable from the data store. You can talk to SQLServer and Oracle. I've worked in 14 languages in my career and Access is hands-down the most effective rapid-prototyping environment so far ... and you can use it for production work with the right plan in place. I'm surprised that we never pushed Microsoft hard enough to port this to OS X because there's nothing like it on the market. If you need to do something clever, definitely get a Windows and Office Home Edition license and start using it. The query builder is awesome. Creating forms is easy. VBA is very flexible. There are plenty of users out there and plenty of examples if you need VBA code. Go for it.