Information content of this page still in editing.
The MS-Access implementations of the database apply a classic
split-database
design. All information about form structure,
VisualBasic code related to automation, etc. is placed in the
client
database installed at the client
workstation. Data traffic on the network is limited to data the
client
requests from the server
.
The central use of record selection tools serves to reduce network traffic generated by use of the database.
In typical use, every user request
for records to edit, include in a report, etc. is
issued from a record selection
form designed to
assist/encourage retrieval of a small number of records
from the database server
.
This differs
from the most MS-Access applications
used by non-profits, which routinely pass
full tables of data from server
to
client
.
The database is designed to facilitate execution of
filter
queries on the server rather than
on the client
computer. MS-Access report generation
otherwise typically passes data from server
to client
for client-side processing of filters.
This design
reduces the data volume being passed across the network.