Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
FULL JOIN is strange
Message
De
06/10/2003 07:01:55
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
 
 
À
04/10/2003 19:24:10
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00835102
Message ID:
00835297
Vues:
15
>I actually had a situation where I needed a full join. I was woking on year end reporting for our payroll product. I need to create XML that includes State info for each employee. The state section of the XML has tags for both State Income tax and Unemployment Insurance tax. The wage and tax amounts can be different. However, it is possible to pay SIT in one state but not have SUTA... So, for each state the employee working in, when I joined the SUTA records to the SIT records I need a return for each state that they had SIT/SUTA even if they only had one tax or the other, hence the FULL JOIN.
>
>BOb

I am not sure I understand correctly. I think you are joining employee with states, twice, for two fields? If that is it, that would be two left joins to avoid omitting employees.
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)
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform