You are miss understanding a bit of what it meant here.
The above is saying to not use the look feature AT THE TABLE LEVEL.
You most certainly will as a matter of general design use lookups, but NOT
at the table level. You will, and should have tons of lookups in your
application. The above is simply saying don't use the table lookup feature.
In other words, don't define the lookup in the table design view.
You don't have this feature in Oracle, or in Sql-server. If you start using
the feature in ms-access, you will wind up with a mess.
You most can, and certainly will use joins. You most can, and certainly
will use combo boxes to lookup values. You most can, and certainly will use
joins in sql to lookup values.
You most can, and certainly will set relations in the query builder.
So, a very large portion of the time you will still use a combo box to do a
lookup. You should, and will have tons of look ups in your application.
The very essence of a relational database is relations to other tables.
However, don't touch that built-in lookup feature AT THE TABLE level in
ms-access.
When you drop a lookup field on to a form from the field list view, it gets
turned into a combo box anyway. So, the substitute for this is lookup field
is simply use the combo box wizard. So, AVOID THE LOOKUP feature and DO NOT
define this lookup in the table design. Of course you will define the
relationship
for the tables in the relationships window as always.
Many people state that the reason to avoid using the table lookup is because
then you don't know what is going on. I consider that a lame argument.
You can create views, or "queries" in ms-access that does the join for you.
There is NOTHING wrong with this.
The real reason why you don't use the table lookup feature is because then
you can't get to the actual value used in the table! If you reference the
field you get the lookup value! This is fine if you actually want to the
lookup value, but what if you need the actual value in the table, and NOT
the lookup? You are now in big trouble! Worse, you will find that reports
groups sort on the original "id" value, but display the lookup value!. This
means your sort orders are all messed up. So, you cant sort correctly, you
cant view, or use the id value. Gosh, how do you use the actual vale in the
field anymore? (answer, you can't!). It is a mess if you all of a sudden
need to use the actual field value. These pit falls are only a scratch of
the
problems that this lookup feature brings on.
If the lookup feature is NOT
bothering you, then I suggest you continue developing until you do find this
out on your own. It is not really that bad, and perhaps for some simple
things, it might be ok. The instant you start writing some code and working
with the data, you will hit a wall. This is just one of those things that
you can only learn by doing.
Good luck....and feel free to use the combo box wizard on a form..but go
near that lookup feature at the table level.
