It checks for Application.cfm on Linux. That's just the way it is. Glad you found the problem, way to go!
M -----Original Message----- From: Randell B Adkins [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 10:56 AM To: CF-Talk Subject: Re: Signal 11 & CF Services? (Might be Solved) Well maybe someone can explain this... First off I think I have isolated the problem. It was not the request scope or the database in this case. So far I have ran 2 successful tasks with just a Query Tag. I am running a final test with both a Query and CFMAIL. Given the fact that Linux is Case-Sensitive, that when CF looks for an APPLICATION tag within the given directory and one does not exists it goes up to the parent level. Which is all fine and dandy... However something I just found out that the first one that Linux looks for is: Application.cfm and if that is not found it will scroll up the chain. It never checks for " application.cfm ". Why is that? The APPLICATION tag in the schedules directory has to be named: Application.cfm and NOT application.cfm My thought would be that Linux would search for the CAPITAL A first as it is before the LOWER A on the ASCII chart. But if the first was not located to look for the second version of the application tag. Then if that is not found scroll up to the parent level. Any idea why Linux requires the A in the Application tag to be CAPPED? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
