NW Data Centric home   home   [about]   downloads  

Current loctn: about > multiuser design

Multi-User Design

Information content of this page still in editing.

Split-Database Design

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 required simply for operation of these application components therefore does not get passed across the local area network. Data traffic on the network is limited to data the client requests from the server.

Record Selection Tools

The heavy use of record selection tools is partly intended to reduce the amount of network traffic generated by use of the database. In typical database use, every user request for records to edit, records to include in a report, etc. is issued from a record selection form designed to assist/encourage the user to define a small number of records to be retrieved from the server. Only in an unusual circumstance will the client application issue a request that would request a full table to be passed from server to client. This is to be contrasted with the majority of MS-Access applications being used by non-profits, which actually routinely pass full tables of data from server to client.

Report Filter

The approach used to indicate which records are to be included in a report is designed to facilitate execution of filter queries on the server rather than on the client. MS-Access report generation otherwise typically passes data from server to client for client-side processing of filters. When fully utilized, this design will result in dramatically reduced volumes of data being passed across the network from server to client.