That's what we do, too. Any working neo-query.xml file, even one from another server with different datasources will "work" - all it has to be is non-corrupt.
We put a readonly copy of neo-query.xml, renamed neo-query.xmlSAVE in the same directory with neo-query.xml so it's always ready to be used. (Just specifying neo-query.xml as readonly doesn't work as CFMX strips the readonly protection off) Chris Norloff ---------- Original Message ---------------------------------- From: Dave Watts <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Tue, 7 Dec 2004 14:33:11 -0500 >> Does replacing the corrupt neo-query.xml file with a recently >> backed up version fix the problem (till MM provides a more >> permanent solution)? We are about to migrate to CFMX. Maybe I >> should I get familiar with this process . > >Yes, that has worked for me every time so far. This has been a pretty rare >problem for me. > >Dave Watts, CTO, Fig Leaf Software >http://www.figleaf.com/ >phone: 202-797-5496 >fax: 202-797-5444 > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - CFDynamics http://www.cfdynamics.com Message: http://www.houseoffusion.com/lists.cfm/link=i:4:186546 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
