Using outer joins is the correct solution,
however, since (as pointed out by Jamileh) outer joining seven tables can get a
little ugly, I would suggest that when a user starts the process you add a
record to all 7 tables. This will setup the IDs and make your joining easier.
Then add a column to each table which is a boolean “complete”.
Once you retrieve the content of the 7 records, test the 7 complete flags to
see what has been done. Of course you would initialize the complete flag to
false (0), and the set it to true (1) when the user has completed that stage. I find that it’s generally better
practice to explicitly mark a record with a complete flag, rather than depend
on the presence or lack of a record to determine if something has been done. Robert -----Original Message----- You'll have to use outer joins
between your tables. It'll look something like: FROM tblOne LEFT OUTER JOIN tblTwo
ON tblOne.ID = tblTwo.ID LEFT OUTER JOIN tblThree ON tblTwo.ID = tblThree.ID and so on. You're telling it to take ALL
records in tblOne, not just the rows with data in both tblOne and tblTwo, and
et cetera. I'd suggest building one join
at a time and testing it before you add the next - these things can get ugly. jamileh -----Original Message-----
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf |
Title: Message
- Witango-Talk: Multiple Table Search Results Cecilia Cos
- RE: Witango-Talk: Multiple Table Search Resul... Wilcox, Jamileh \(HSC\)
- RE: Witango-Talk: Multiple Table Search R... Robert Shubert
- Re: Witango-Talk: Multiple Table Sear... Stephen Su