My Assistant
![]() ![]() |
|
|
Mar 28 2012, 04:09 PM
Post
#1
|
|
|
UtterAccess Addict Posts: 114 |
Hi,
In my web database I was getting unpredictable results with my query. Certain results that displayed as expected would suddenly be filtered out when I added another table. I noticed the relationship of the new table had redundant joins to other tables, so I deleted them. Now my query looks as it should. Am I correct in assuming that changing or deleting the table relationships shown in the query design have no effect on the relationships of the tables outside the query? Thanks |
|
|
|
Mar 28 2012, 04:13 PM
Post
#2
|
|
|
Rent-an-Admin Posts: 8,778 From: Banana Republic |
The lines you see in your queries are not relationships but rather joins.
Think of them this way - Relationship describe how one entity _ought_ to map to other entity. Join describe how one entity _should be_ matched to other entity. In a web database, the only place you create a relationship is when you create a lookup field, and Access defaults is to auto-join any query that has both participating table based on the lookup field. But join only describe how you'd get the data back (e.g. should you only see matches or should you see possible records from one table regardless if they have a matching entry in other table or not?) HTH. |
|
|
|
Mar 28 2012, 04:33 PM
Post
#3
|
|
|
UtterAccess Addict Posts: 114 |
Ah, Thanks. I understand now. Initially, I did not even think of deleting the joins because I thought they were hard-wired into the actual tables.
|
|
|
|
![]() ![]() |
|
Go to Top · Lo-Fi Version | Time is now: 25th May 2013 - 04:34 PM |