L
Larry Filoso
A common design in Access is to create a main form in form view to display
one parent record, and a subform in continuous view to display related
children records. The Link Master/Child Fields properties provide the keys to
filter the children records related only to the parent record displayed.
In an .mdb, Jet downloads all child records, but filters display in the
subform as each parent record is chosen. Does an .adp work the same way? If
so, to reduce network traffic, should the programmer manually set the
recordsource of the subform to download only the related children records?
Example: code in .AfterUpdate of a pick list combo box sets the recordsource
for the main form to a specific parent record ("SELECT * FROM dbo.[RS
function](1)" with 1 as Primary Key value record identifier) AND the
recordsource of the subform (Me![SF Ctrl].Form.RecordSource = "SELECT * FROM
dbo.[Child RS function](1)" where 1 is the foreign key value relating
children recs to this parent record. (Link Master/Child Fields property left
blank.)
one parent record, and a subform in continuous view to display related
children records. The Link Master/Child Fields properties provide the keys to
filter the children records related only to the parent record displayed.
In an .mdb, Jet downloads all child records, but filters display in the
subform as each parent record is chosen. Does an .adp work the same way? If
so, to reduce network traffic, should the programmer manually set the
recordsource of the subform to download only the related children records?
Example: code in .AfterUpdate of a pick list combo box sets the recordsource
for the main form to a specific parent record ("SELECT * FROM dbo.[RS
function](1)" with 1 as Primary Key value record identifier) AND the
recordsource of the subform (Me![SF Ctrl].Form.RecordSource = "SELECT * FROM
dbo.[Child RS function](1)" where 1 is the foreign key value relating
children recs to this parent record. (Link Master/Child Fields property left
blank.)