>As far as me using the FULL JOIN I showed an example to Naomi and she agreed that FULL JOIN will work better for me. I can dig out that example and present it here again. But in description the reason I need FULL JOIN is that both the table on the LEFT and RIGHT of the join have unique/different records. And I am trying to create a query/cursor that will have unique records from both sides. This is why FULL JOIN works for me.
Yes - that is the basic idea of a FULL [OUTER] JOIN (get data from both sides, whether there is an equivalent record on the other side or not). I have not met a situation where I needed one, but perhaps you did.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
