> Also consider changing to Application.cfc its more usefull > and more commonly used on new applications.
Assuming the new server is a new enough version that may be an option. The cflocks around the application variables hint that this app originated on ColdFusion 4 or 5, probably a legacy app developed a long time ago. If it's still running on an older version of ColdFusion then CFCs won't be an option, though if it's being migrated to a more modern version then it becomes possible. You also have to look at what value application.cfc provides over application.cfm. For a legacy app like this, probably not much, if any, as there is the chance of something that works fine now breaking in that transition. @John - Application.cfc has a completely different structure than Application.cfm, so renaming the file isn't going to do anything for you. The CFC version can accomplish the same thing as the CFM version but is more structured. If your app is working fine as-is then I wouldn't worry about refactoring it unless you're planning more extensive upgrades to the application. -Justin ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-newbie/message.cfm/messageid:5512 Subscription: http://www.houseoffusion.com/groups/cf-newbie/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-newbie/unsubscribe.cfm
