master-detail and lookup, but not on foreign key
281235Feb 9 2003 — edited Feb 12 20031) Seems like it is impossible to create a master-detail relation between two module components, if a foreign key relationship does not exist.
In my specific case the master is a view which has columns something like (but much more of them, and much more complicated): view [abc(col1,col2,col3,...,id,...col76)]. I created the view by hand, and copy-pasted it into Designer as a view based on my own sql definition. Then I want to show the details from a table [emp (id,name)] via join (abc.id=emp.id).
This is easily doable in Forms, but it's impossible in Designer. Any specific reason? Should I try it another way?
2) Similar question but for lookup table usages?
Example (primary keys are inherited from the "master"):
ABC (#ABC_ID, Name)
ABCD (#ABC_ID,#ABCD_ID, Name)
ABCDE(#ABC_ID,#ABCD_ID,#ABCDE_ID, Name)
So, I don't want to do it this way:
ABCDE >---- ABCD >---- ABC
just in order to show a LOV list for the Name in ABC (because this is impossible as Designer suggests - ABC is not a base-table usage and items cannot be insert,update etc.)
I would like to do it this way:
A >---- ABC
B >------ ABCD
C
D
E
and just do a validation and LOVs in a partial manner, or something like that - if you understand what I mean?