if the code, as it is now, is as efficient as your reorg way, I would leave it alone and come up with a way record the url params and analyze them. Why re-do it?
A stored procedure in the application.cfm file might work well. There might even be a way to record the url params in the log file(maybe sys admins can shed some light here.) anyways, my $0.02 ============================================ Greg Jordan Macromedia Certified ColdFusion Developer Web Project Manager [EMAIL PROTECTED] Unified Health Services 51 Germantown Court Cordova, TN 38018 PH - (901) 843-2667 x261 FAX - (901) 843-2672 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 04, 2001 1:58 PM To: CF-Talk Subject: <CF_Pass_Parameters_to_Index.cfm> HELP I have recently joined a company that had their site built by a consultant agency. This agency build 95% of the CF/dynamic site pointing to the .com/index.cfm file. The parameters that are passed through the URL determine the look and feel and the content that's shown on the page. I under stand how all this works, and it's efficient, but the Web log files are not allowing me to show mymanagment team the details of the traffic coming to the site. The log files show the number of times the index.cfm file is requested, but naturally doesn't detect the parameters being passed through the URL. I'm ready to reorg the code so that it does call a different *.cfm page each time. Does anyone have any tips or suggestions? Thanks ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
