Continuous Child Input Form

[Pisteuo]

I need to add text controls to a continuous query subform for additional user input.

The user types Asset_No into Form1. Subform1 queries a list of circuits and descriptions for user reference. I added subform2 with the control source as a table for additional input for the key "circuit". My intention was to line the two subforms side by side to be seamless for the user.

Subform2 is a subform to Form1 and not a sub-subform to Subform1 because I need the two subforms to be continous.

I have linked Subform2 to Suform1 this way:
Link Child Fields: Circuit
Link Master Fields: Subform1.Form!Circuit

My Problem:
Subform1 queries all circuits based on Form1.Asset_No as it should.
Subform2 allows input for only the first circuit shown in Subform1 though it is a continuous form.

Can I make Subform2 show all the circuits from Subform1. Or is there a more efficient way I should be going about this all together? Thank you.

 

[Galaxiom]

Although it is a continuous form the link fields limit the records to those that match the link. The link is really just another manifestation of a Where clause applied to the RecordSource of the subform, as in:

WHERE Forms!formname.Form!MasterField = Forms!Formname!Subformname.Form!ChildField

Multiple field names can be separated by semicolons.

The link is normally used to make a single view subform track the current record in the main form. As each record is selected in the list the subform switches to match it. It is so you don't need a continuous editing form which is probably more appropriate for your use anyway.

Otherwise, to make your continuous form continue to display all records but move to the same record as the first subform you need to run an OnCurrent event procedure of the first form. It will need a GoToRecord or FindRecord command in the second form.

You would need something similar to make the first subform track the second when you moved to a new record in the second subform.

 

[Pisteuo]

Thank you Galaxiom for addressing my problem with those two options. I think you are correct that the edit form should be single. This will cut down on mistakes with key order and other possible user obsticles.