JMongi
Active member
- Local time
- Today, 09:50
- Joined
- Jan 6, 2021
- Messages
- 802
So I've been rooting around in the northwind sample database to get some ideas and feel for form interactions and such.
One thing I noticed is that there are a lot of specified non default joins. I understand the general ideas of inner/outer joins. But, they use them in areas I hadn't really thought about. As an example, there is a lookup table called "Purchase Order Status". That is connected in a 1:M relationship to table "Purchase Orders". Here's a pic:
So, if I understand correctly, a default query will pull all the records from PO and just the matching ones from PO Status.
I've always just did a default match join. It's seemed to work fine so far. But, maybe I've been doing it wrong. Can anyone fill in the blanks for me? They do the same thing with most other lookup type relationships. But, then, the "inventory transaction types" lookup table is a default join to the "inventory transactions" table. Just trying understand the thought process behind choosing the join type.
One thing I noticed is that there are a lot of specified non default joins. I understand the general ideas of inner/outer joins. But, they use them in areas I hadn't really thought about. As an example, there is a lookup table called "Purchase Order Status". That is connected in a 1:M relationship to table "Purchase Orders". Here's a pic:
So, if I understand correctly, a default query will pull all the records from PO and just the matching ones from PO Status.
I've always just did a default match join. It's seemed to work fine so far. But, maybe I've been doing it wrong. Can anyone fill in the blanks for me? They do the same thing with most other lookup type relationships. But, then, the "inventory transaction types" lookup table is a default join to the "inventory transactions" table. Just trying understand the thought process behind choosing the join type.
Last edited: