Hi,
The greatest book is probably the query designer, at least, for start.
Bring the two tables in a new query of the query designer, the one having
the original values, and the one having the Translations (with fields Old ad
ToBe).
In the upper part, select the field to be translated, and drag and drop it
over the field 'Old'. That creates a join between the two tables. An inner
join, in fact. An inner join can be seen as some kind of lookup, or
translator, when used to reach another field, here ToBe. So, in the grid,
now, drag fields you need, including the field ToBe, from the table of
translations.
That's all.
You can take a look at the generated SQL.
Sure, that does fine for simple SQL statements, but for more, you can take a
look at Queries for Mere Mortals:
http://www.amazon.com/gp/product/product-description/0201433362/102-2353860-8771305?redirect=true
For really advanced stuff, I suggest Joe Celko books
(
http://www.amazon.com/gp/product/1558605762/102-2353860-8771305?v=glance&n=283155
and
http://www.amazon.com/gp/product/1558604537/102-2353860-8771305?v=glance&n=283155
and more specialized,
http://www.amazon.com/gp/product/1558609202/102-2353860-8771305?v=glance&n=283155).
You can also hang in newsgroups like this one and the one about MS SQL
Server, as example, if not to see something about how, something to see
about WHAT can be done in SQL
As for the convention, I personally adopted the one from Joe Celko: key
words in all caps (but I often use As instead of AS ), table name with
plurals, field name with singular: skills, or Skills is a table, skill,
or Skill, is a field, and if a table is a junction table, it is often made
of the two field it holds: SkillsWorkers is a junction table with (main)
fields Skill and Worker, so that one row in SkillsWorkers is about one skill
that has one worker, use has many rows as required to specify all the
relevant skills of a given worker.
Hoping it may help,
Vanderghast, Access MVP