This is part 3 of a series of posts on using the MVC design pattern as inspiration for FileMaker design.

I have been searching since day one for an architecture that can make designing, extending and maintaining a complex FileMaker system easier. I have yet to find one. Sometimes I think FileMaker is too flexible. There are too many easy ways to do things that will absolutely cause you myriads of grief later. I have tried several times to develop my own frameworks, but they always left me feeling like it was too much work.

This is continuation of another post where I introduced the idea of considering the MVC design pattern as inspiration for designing a FileMaker solution.

There have already been some great comments posted on part 1. There have been some very good points made on where there is overlap between FM and MVC and where there isn't. I want to stress that this is an experiment and I want to see where it leads.