A couple other reasons are: 1. Separate queries into their own file in case a dba who doesn't know CF very well can access the queries without messing up anything else.
2. To provide modularity so that the same query can get used in multiple fuseactions. ----- Original Message ----- From: "Douglas Smith" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 28, 2002 5:08 PM Subject: Re: Queries and display files > One reason is so that the index file becomes more self-documenting. You > can see straight from the index file, the dependencies of any given > fuseaction. If you modify a query fuse, you can do a quick scan of the > index file to see which pages/fuseactions it will affect, and you know that > you will need to test those fuseactions also. > > At 02:25 PM 3/28/02 -0600, you wrote: > >I know true FB3 methodology calls for separating query fuses from display > >fuses, but does this not produce more work having to remember to include > >calls to queries 1,2, and 3 before calling display page X? What's the > >reason for not putting all necesarry query calls within the display page > >itself? > > > >Thanks > > > >Tom Schreck > >[EMAIL PROTECTED] > >817-252-4900 > > > >I have not failed. I've found 10,000 ways that won't work. > > > >- Thomas Edison > > > > > ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
