I am trying to prune my database and I want to know what I can delete. There is a script for example and in the DDR it tells me on what layouts it is, and scripts that use this script, both of which are extremely handy. If you just add Buttons that use this script that would make it complete!
Until then, I won't be able to delete my 30 scripts that I don't know whether they are used on a button somewhere and a user will freak out if I delete it! hahaha
Oho. Yes I did not guess I could vote for my own Idea. Who would had thunk?
Here is a tool for you.
I am playing around with this, it seems not so fast on very low power php host if there are many files (I need 54sec for 48 files some time).
Anyway there is no reverse reference in the file itself, you need to make DDR on all files it could be referring your target file.
And a script can be called from any fmp: URL without FM file for example shortcut on desktop. You can't know it
Also bear in mind that scripts can be referenced from field and layout triggers, file options, menu items, and (of course) other scripts, and also through indirection using the fmp: url scheme as mentioned above, or from some completely external source using php, AppleScript, etc.
I'd love to see a built-in function for this, but in the short term check out an external developer tool (like, for example, my own FMPerception).
Johan Hedman wrote:
use the tool Base Elements for that
dataWolf, there are a handful of third-party tools available for such analysis, most of which rely on the XML version of the DDR, which includes your requested info. For that reason, I'd be surprised if the HTML version of the DDR didn't already include it, but it is possible that is the case.
For what it's worth, this request isn't likely to go anywhere because FileMaker has already announced that it will at some point in the future no longer provide the HTML version of the DDR.
dataWolf
Not sure if Jive will ever follow a logical principal that the Author of a Feature Request always is in favour of his own idea and therefor, should be set to Vote Up per default.
Those anybody know of a developer who would write a Feature Request in order to vote it down ?!