Tom, There are a couple of reasons I do this. First, I can have all my files that have database interactions separate from my code files. That really helps in letting me use query sims and then later come back and fill in the real SQL. Doubly true if there's a DBA involved in the project.
The other reason is for reusability. I often find that I can combine several select queries into a single one that can be used by multiple display files. I don't the earth will end if you decide against doing that, though. -----Original Message----- From: Tom Schreck [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 28, 2002 3:25 PM To: [EMAIL PROTECTED] Subject: Queries and display files 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 ==^================================================================
