Problem with FldRef.RELATION

Timo_Lässer

I have a problem with FieldRef.RELATION.
I want to know, if a Field has a relation to another table. Therefore I use the FldRef.RELATION to find out the Table No.
If the field has a relation, all works fine. But if there is no relation, the fin.exe crashes.
I use 3.70 incl. HF12 (newest Runtime).
What's wrong?

RecRef.GETTABLE(MyTable);
FldRef := RecRef.FIELD("Field No.");
IF FldRef.RELATION <> 0 THEN BEGIN  // <-- fin.exe crashes here if RELATION is 0
  [...]
END;

lakshmivalluru

i get the same error

eromein

It's a bug... that's what is wrong.

You should post it on the MBS bug report system and hope they will fix it.

Timo_Lässer

Thanks for your reply.
I have already posted this in the partnersource but I expected that anybody have a workaround for this issue.

If anybody of you has further informations (or a workaround) to this, please let me know about this. (If I have news, I will post them here.)

kine

Look into table 2000000041 - Fields - there are all infos you want... 8)

Timo_Lässer

kine wrote:

Look into table 2000000041 - Fields - there are all infos you want... 8)

The Field.RelationTableNo doesn't show a Table No. if it is a conditionally Relation.
I have some cases where the RelationTableNo is empty but the FldRef.RELATION has a value <> 0.

kine

Sorry, i forget this situation... yes, it must be found dynamicaly and this in table Fields is not possible.

This bug is old, no response from MBS... hmmm, this will be problem, sorry, cannot help you... :?

Timo_Lässer

kine wrote:

no response from MBS

This is not quite correct
Today, I got the following answer from the Support:

MBS-Support wrote:

This issue will be corrected in the next release.

In fact, this doesn't help me, but it is a ray of hope.

eromein

guys,

I'm not sure but please keep it in mind. I think the relation field in the "field" table is not always correct. I think.... (I THINK) is ofter not filled or 0 when there should be a value.

Just check it please!

Timo_Lässer

eromein wrote:

[...] the relation field in the "field" table is not always correct. [...]

That's what I mean. You cannot use the Field.RelationTableNo because this field is 0 if the Relation depends on a condition.

eromein

Ooooh sorry, just missed that post. Just a tought without checking it myself. Is there a way to find out if there is a condition defined?

Timo_Lässer

eromein wrote:

[...] Is there a way to find out if there is a condition defined?

I think no. :roll: (At least I don't know any way to find it out.)

Gunnar

Moin Moin from the high north,
I has now everything tries out you comes simply not to the TableRelation reliably ran. This problem exists however already starting from the Financials Versions. The problem is which you over the table Field the TableRelation sees, but only if on the TableRelation no filter is. (here you could look at times the field Base Unit of Measure in the article, you no TableRelation there will unfortunately be). You come however neither over the Fieldref functionality nor over the Rec. TableRelation to the TableRelation ran.

eromein

Ooooh darn, didn't realize this was a german forum. If I had known, I would have posted everything in german.

Ooooh wait... It's English :shock:

krichter

Maby not relevant any more but a possible workaround could be:

...

Field.GET(RecRef.NUMBER,FieldRef.NUMBER);
IF Field.RelationTableNo <> 0 THEN
MESSAGE('Field %1 has relation to table %2, field %3',Field."Field Caption",Field.RelationTableNo,Field.RelationFieldNo);

...

Field : Record 2000000041

Timo_Lässer

krichter wrote:

Maby not relevant any more but a possible workaround could be:

...

Field.GET(RecRef.NUMBER,FieldRef.NUMBER);
IF Field.RelationTableNo <> 0 THEN
MESSAGE('Field %1 has relation to table %2, field %3',Field."Field Caption",Field.RelationTableNo,Field.RelationFieldNo);

...

Field : Record 2000000041

This only works if the property TableRelation of the field has no condition or any other filter.
So, you cannot use this workaround if you use RecordRef / FieldRef.

kine

krichter wrote:

Maby not relevant any more but a possible workaround could be:

...

Field.GET(RecRef.NUMBER,FieldRef.NUMBER);
IF Field.RelationTableNo <> 0 THEN
MESSAGE('Field %1 has relation to table %2, field %3',Field."Field Caption",Field.RelationTableNo,Field.RelationFieldNo);

...

Field : Record 2000000041

If you read previous messages, you can see, that Tab. Field is not solution... 8)