Thank you for helping with this. Hear are my thoughts. If I override everything, when it comes to upgrade time, it will be easy to know exactly what I have customized because prior to upgrade, I can use Winmerge (http://winmerge.org/) to identify the files in the /CUSTOM directories that have changed from their original default states by having Winmerge automatically compare them to the files in the original default (ie, /Classic) directories. So, I don’t see this as a problem. The advantage of the override everything approach for a newbie like me is that I will be 100% confident that all customizations and changes made through use of the admin console will be reflected in the files in the /Custom directories. If there is no increased performance overhead then this seems like a good idea. Also, this seems like an approach which is less prone to error on my part by inadvertently changing a parameter stored in an /Classic file via the admin console. Otherwise, prior to each and every change made via the admin console won’t I need to check to make sure that I had previously copied (overridden) the relevant file to the Custom directory?