L
Larry
I'm working with an application composed of a "client"
Access database and a "server" database containing all
data to be worked with. The goal is to place the "server"
database on a computer accessible from a number of
workstations on the local area network.
I'd like to minimize the amount of data passed over the
network. Typically, I'm sending the user to a single,
specifically queried "master" record, and then would like
to provide access to several "related" tables using linked
subforms of a "list" style. I was hoping to limit the
data retrieved from the server for each subform to only
those rows that are related to the current "master"
record.
Do I need to take special steps to ensure that result, or
will the default operation of these subforms accomplish
that? I'd like to prevent ALL data from each related
table being passed from server to client when the form for
editing a single "master" record is opened - this just
seems like needless network overhead...
Thanks in advance for any info...
Access database and a "server" database containing all
data to be worked with. The goal is to place the "server"
database on a computer accessible from a number of
workstations on the local area network.
I'd like to minimize the amount of data passed over the
network. Typically, I'm sending the user to a single,
specifically queried "master" record, and then would like
to provide access to several "related" tables using linked
subforms of a "list" style. I was hoping to limit the
data retrieved from the server for each subform to only
those rows that are related to the current "master"
record.
Do I need to take special steps to ensure that result, or
will the default operation of these subforms accomplish
that? I'd like to prevent ALL data from each related
table being passed from server to client when the form for
editing a single "master" record is opened - this just
seems like needless network overhead...
Thanks in advance for any info...