Subject | Master detail problem when lenght of the link field is more than 25 chars |
---|---|
Author | Mihai Chezan |
Post date | 2004-08-03T18:49:55Z |
CREATE TABLE dep (
id_dep INTEGER NOT NULL,
name VARCHAR(50) NOT NULL,
CONSTRAINT dep_pk PRIMARY KEY (id_dep)
);
COMMIT;
CREATE TABLE person (
id_person INTEGER NOT NULL,
name VARCHAR(50) NOT NULL,
id_dep_123456789_123456789 INTEGER NOT NULL,
CONSTRAINT person_pk PRIMARY KEY (id_person)
);
qryDep - master
qryPerson - detail
Master Links:
person.id_dep_123456789_123456789=dep.id_dep
When I open qryPerson I get this error:
FieldName: MLNK_ID_DEP_123456789_123456789_0 not found
I think the problem lies in the way IBO names the parameter for the
detail:
MLNK_ID_DEP_123456789_123456789_0 = 33 chars
If the detail has the link field named:
id_dep_123456789_12345678 then it works.
So if the link field from detail has the length <= 25 it's ok.
Question: Can I tell IBO how to name the master detail parameter from
the Master Links?
Test case uploaded: Problem-MasterDetail.zip
ps: I really have fields that are more than 25 in length.
id_dep INTEGER NOT NULL,
name VARCHAR(50) NOT NULL,
CONSTRAINT dep_pk PRIMARY KEY (id_dep)
);
COMMIT;
CREATE TABLE person (
id_person INTEGER NOT NULL,
name VARCHAR(50) NOT NULL,
id_dep_123456789_123456789 INTEGER NOT NULL,
CONSTRAINT person_pk PRIMARY KEY (id_person)
);
qryDep - master
qryPerson - detail
Master Links:
person.id_dep_123456789_123456789=dep.id_dep
When I open qryPerson I get this error:
FieldName: MLNK_ID_DEP_123456789_123456789_0 not found
I think the problem lies in the way IBO names the parameter for the
detail:
MLNK_ID_DEP_123456789_123456789_0 = 33 chars
If the detail has the link field named:
id_dep_123456789_12345678 then it works.
So if the link field from detail has the length <= 25 it's ok.
Question: Can I tell IBO how to name the master detail parameter from
the Master Links?
Test case uploaded: Problem-MasterDetail.zip
ps: I really have fields that are more than 25 in length.