Restricting entry child records

[DORaymond]

If a set layout has the following structure: Header table 1:M child table 1:M grandchild table, is there an easy way (action scripting?) during data entry to be sure that a user cannot enter data in the grandchild table without first entering a record in the child table. In other words, I do not want to have the possibility of orphan grandchild records.

Thanks for your help.

[Stan Mathews]

Re: Restricting entry child records

If the data entry takes place in a form or browse based on the set, Alpha creates the child and grandchild records (set composite record) automatically. No action (scripting or otherwise) necessary.

[DORaymond]

Re: Restricting entry child records

Stan - Yes, I agree. What I am asking is: If a form contains header records, an embedded browse (1:M) for child records, and an second embedded browse (1:M) for grandchild records, if a header record is entered, there is nothing stopping data entry directly into the grandchild browse (skipping the child browse). Doing so will enter a record into the grandchild table, but the record will be orphaned (no child record linking header to grandchild).

[Stan Mathews]

Re: Restricting entry child records

You could make the child to grandchild linking field required in the table field rules or

code the form's cansave event

DIM SHARED atest AS c
atest = [COLOR="Red"]Field1[/COLOR].value
if alltrim(atest)=""
	ui_msg_box("Alert","Must fill in [COLOR="red"]field1[/COLOR]")
	cancel()
end if

where field1 is the objectname of said field. (inline xbasic action scripting element)

(Do you have an aversion to posting in the forum for the Alpha version you are using? (this is the general database design forum)

Database Design (1 Viewing)
Forum for questions about general database design. Specific questions related to Alpha Five should be placed in the appropriate Alpha Five forum

[DORaymond]

Re: Restricting entry child records

Stan - I will give it a try. I am using A5V4.5, but that forum is not visited by many very often. Our company owns a copy of A5V8, but our mission critical application does not work correctly using it.

Thanks for your help.

[Stan Mathews]

Re: Restricting entry child records

The A5V4 forum doesn't have many new posts but the software used for this entire board alerts us when there is a new post by changing the forum icon color.

I believe most who try to help out will try to answer just as quickly if a question is posted there.

Let us know if the suggested solution doesn't work. So many factors can come into play.

Another thought is to disable or hide the grandchild fields, initially, and then enable or show them once the child fields are populated.