Business Solutions | Dashboard | Database Conversion | Database Consultant

<p><a href="http://www.skeletonkey.com/blog/taming-the-filemaker-beast"><br /><h1>Taming the FileMaker Beast</h1>

<p></p></a><br /><a href="http://www.skeletonkey.com/images/Blog/hulkmoviewide_480_poster.jpg"><img width="275" height="138" src="http://www.skeletonkey.com/images/Blog/hulkmoviewide_480_poster.jpg" /><br /></a></p>

<p>I'm running into this scenario a lot lately. I think it's because FileMaker 12 is changing the landscape, but it's worth taking a look at in any case.</p>

<p><b>The Scenario</b><br />You have a FileMaker solution that was started in FileMaker 4 or 5. It's been enhanced and modified several times since then, and extended over the course of a decade or more by a handful of developers with varying levels of skill. The system is robust, and helps manage critical components of your business. Now, as the system has aged, you're running into questions:</p>

<ul class="content_list">

<li><i>Is it me, or is the system not performing as quickly as it used to?</i>

</li><li><i>Didn't we just restart the FileMaker Server a week ago? What's up with that?</i>

</li><li><i>Should we upgrade to FileMaker 12? What's the conversion process look like? More importantly, will anything break?</i>

</li><li><i>Is it time to rebuild?</i>

</li></ul>

<p><a href="http://www.skeletonkey.com/blog/taming-the-filemaker-beast" target="_blank">read more</a></p>

Source