Is it true when using Natural links to link the parent and child together you MUST use the form with the subform to maintain the link?

Sunnyjena was having problems with her data. When she entered her inv data from the form with the natural linked inv subform  the data was visible when she searched the client at a later time.

When she had a data entry person enter data directly to the inv database even though they entered the Client number in the record it did not pull up when the client was searched from the form with the subform. (if a relational link was used with the client number as the key it would have worked as she had believed it would)

I believe my response to her should be that Sesame is functioning properly. It is just a mater of entering data incorrectly.

I was paranoid of giving out wrong info so I  suggested to her we should confirm this with the experts on the forum and widen this discussion to more then her and I.

So all please feel free to chime in.   

Thanks

If my understanding of natural links and data retention  is correct I can see the importance of being able to remove item choices from the command tree to protect against this type of error.

Quote:


That sounds like a helpful command. Thanks

I am sure with a little thought and training there are many ways to protect against data errors.

Thanks for the new programming example Snippet on Preventing certain Users from adding new records. This gives us another tool already.

Quote:


To follow the example in the Additions guide In the most basic form of use.

// Create a button element on the parent form that contains the subform. Place this
//  code on on element entry of button element.

var nn as int  //Create variable

nn = @formnewrecord("formname")  // enter your form name as it appears on the menu

// This will when clicked add a new record to subform. Be careful however because if the subform is on a tab (I believe yours is) even if the subform is not visible it will add a record.(it is easy to repeatedly click the button till you figure out your on the wrong tab)  If there is any on entry logic it is easy to create junk records.

Found and fixed.

@FormNewRecord and NewRecord both have to turn off event programming while they are in operation (a very brief moment). @FormNewRecord found a way around turning event programming back on again.