Re-Thinking is the new Rebuilding | the beezwax buzz

Re-Thinking is the new Rebuilding

Posted by vince 06/18/2013 at 11:22AM

Republished from the original InspectorPro Wiki article.

Sometimes you just need to start over and to take a fresh look at how you are doing things. Many of you know that I usually like to start things anew, but its also understandable that this is impractical at times.

However, with the release of FileMaker 12, I was inspired to dive deep into how InspectorPro 4 (IP4) was architected and change my way of thinking. It isn’t about REBUILDING per se, but rather this is about RE-THINKING your solutions as you move to FM 12.

At its core, InspectorPro is itself a FileMaker database. The previous version, Inspector Pro 3 (IP3) was originally architected as FileMaker Pro 7 file, and continuously remodeled as we moved all the way through FileMaker Pro 11. InspectorPro 4 on the other hand was built as a FileMaker 12 solution.

I wanted to tell you more about the approach I used. Hopefully it will give you some ideas as you start to re-think, and ultimately rebuild, solutions in FileMaker 12.

Re-thinking InspectorPro 4 in FileMaker 12

In ‘re-thinking’ IP4, with FileMaker 12, I was able to do a number of things. Primarily I was able to dramatically improve performance over IP3. There were a number of contributing factors that led to this improved performance. But one of the core changes was the very extensive use of the new ExecuteSQL function in FileMaker 12.

via Re-Thinking is the new Rebuilding | the beezwax buzz.

Liked Liked
Need FileMaker Development Help? Or to purchase FileMaker Software?
Contact FM Pro Gurus for help