nstefaniuk suggestion is correct. However, I'd rather use a mapping table. Depending on the size of the data set, JOINs in QlikView use a lot of disk space making the application bigger. The result, if the data model is correct, will be the same:
MAPPING LOAD [Code Station], StationRap FROM [..\..\Code stations MPP.xls] (biff, embedded labels, table is Sheet1$);
Qualifying prefixes each filed with the name of the table. See this example:
FROM File.qvd (qvd);
Will create a table "Data" with fields "Data.Field1" and "Data.Field2" instead of the normal "Field1" and "Field2". As opposed to traditional SQL, where many tables may share many field names, and you need to specify which field does the relationship, QlikView links automatically tables when one or more fields are named the same.
I was talking about SQL, not QlikView. In SQL you need to specify the key fields in each table, irrespective their name. Not in QlikView, where two tables links were the name of at least one field is the same.