Unqualified fields not working as key

[#1]

Hi everyone, I've this issue with keys that dont match when it should...!

I've several tables related throught the field date in its separated form: year, month, quarter and others. The problem is that with only a table, the relation is not working and when I create a table with all the fields including the unqualified one: year, it appears -, representing null.

eg:

as you can see, the field named anno is the one it supouse to work as key with the rest of the model; anno_copy it's the same field but unqualified. So, how and why come that the field anno appears as null in all the rows if it real value is 2010..??? why is not taking the relation?

I appreciate in advance your response! Regards!

[pover]

Leonor,

This sure seems crazy. To help to see what the problem is if you load only PAGOS do you see values in anno? Does anno_copy still give you values when you concatenate? Does the field VRENG_PAGOS.anno exist?

Try not using qualify and to indentify if a mont_doc is from PAGOS you should create an additional field like

'PAGOS' as [Document Type]

Regards.

[#3]

Hi Karl, first of all, I'm very grateful for your disposition to help.

Secondly, I've check every line on the script and found out that the problem were when I created the QVD's (no way of you to see it). Wich was the problem? well, when doing the mapping for the field trimestre (quarter) of the table PAGOS, I missed a letter of the name map table, instead writing quarter_map I wrote quarter_ma.

I noticed because I started to unqualify each field at the time, and was with trimestre that all gone null.

I'm sorry for all the trouble and all the thoughts of: what the hell is happening here!?

Thxs for your responses

Regards