AnsweredAssumed Answered

Force relationship between 2 related tables from the master to the detail 1:M

Question asked by courdin on Oct 29, 2016
Latest reply on Oct 30, 2016 by BruceHerbach

The primary table is "profile" which will only ever have a single profile record


it has a 1:M relationship with Activity table and Nutrition Table

( as well as 4 other tables but don't need to discuss them because if we can solve for these 3 tables we can apply the same logic to the other 4)


The Main menu starting form has a menu link to each of the main layouts ( profile setup , and 1 for each of the 6 detail tables)


The Profile layout is typically only visited once during initial setup


Each subsequent use of the app the user would go directly to the Activity layout or the Nutrition Layout


we would like to "auto force" the UniqueID from Profile into the new activity record or the Nutrition layout without the user having to view/navigate through the profile table


Since it will be a mobile app .. screen real estate usage if very critical .. and simplicity for user navigation is a must