I use Base Elements to Analys my solution. It gives me all Error, Unreferenced Items, Warnings and parts where I can increase Performance. There are numerous other tools also
1 of 1 people found this helpful
Sounds like you have a FileMaker system that has lots of value...along with some “technical debt”...
This podcast episode talks about Technical Debt, and some strategies for “paying it down”
This blog post...
Renaming FileMaker Objects Without Breaking Code
...might help guide you way from a technical point of view. (renaming and removing follow many of the same rules)
I recommend that (early in the process) you focus lots (but not all) of your efforts on removing unused layouts. Removing layouts has a cascading effect. Removing a layout will usually remove buttons that call scripts, fields, etc. that are revealed to be unused, etc. For this reason, it is usually best to work is in rounds, layer by layer.
Almost all FileMaker systems can be brought up to standard ( without rebuilding from scratch or breaking functionality) to the point where that they can be easily maintained and added to going forward
Some of the tools we currently use for what you describe:
* BaseElements https://www.goya.com.au/baseelements
* Developer Tool assistant http://www.dracoventions.com/products/2empowerFM/family/developer.php
* Some proprietary, non-commercial tools (and techniques) that we have developed for this type of project that help identify what layouts and scripts are NOT being used, by whom and from where.
We also have some tools for refactoring FileMaker code objects. More on all that another time.
I have heard and seen good things about FMPerception which is already good and in active development. I am hoping that it will become AppleScript’able so that I can extend it in the same way that we extend BaseElements in clean up projects.
http://twdesigns.com/freebies/FileMaker_BaseElements_Toolkit.php (Please excuse the user interface...video from years ago)
Hope that helps.
Tony White Designs, Inc
thanks for reposting your blog, Tony!
Thank you, Malcolm.