but you already knew that :)<BR><BR><BR>what i was trying to get at is. IF the join is very involved, and requires more than you might need, you might as well have seperate queries.<BR><BR>and have you ever heard of a compound command statement??<BR><BR>
Will a compound command statement give you a reasonable alternative to a JOIN. Is it possible? Sure. There are always outliers. Is it likely? No. Unless...Well, the only situation that I can think of where this might come into play in ordinary use would be if you're dealing with one-to-many data. Ok, so it makes sense in that case....But hopefully, no developer would consider using a JOIN in that stuation, which makes my point still valid. Situations in which a JOIN would be reasonable, it's almost always a better solution than multiple resultsets.
My family was in town this weekend, in fact. <BR><BR>>got married yet? have kids?<BR><BR>Nope, and nope. You'll be the first to know when it happens. Unless I forget to tell you. Or tell other people first. :-P