As I was working on a newly converted FileMaker 6 database for a customer, I found myself using scripting groups in a way I hadn’t used extensively before. Every new script that I created for the solution went into a new group folder and any script I modified went into a different and newly created folder as well. I then found myself putting all the scripts I hadn’t touched into their own folders.
As a result, I had a folder structure that showed me ...
- all my new scripts in a folder with sub folders based upon their use
- all the modified script in a folder with sub folders based upon their user
- all the scripts I haven’t edited at all in a folder
At some time, I will consolidate these folders ... but ... at this stage ... it really helps to have them separated. For example, I’m added scripting routines that allow me to add someone in the staff file, click a button and have their security settings broadcasted to all the files in the solution. I can create a security script group in one file, copy the entire folder of scripts and paste it into the other files. Very handy indeed!
More info about the author and FileMaker in general, contact me at email@example.com.
© 2008 - Dwayne Wright - dwaynewright.com
The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.
====================== ADVERTISEMENT ==============================
Check out the FileMaker Calculations Explored blog at http://dwaynewright.blogspot.com/ or subscribe via your news reader. ===================================================================