Home > Articles

  • Print
  • + Share This
This chapter is from the book

Understanding the Client/Server Model

The client/server model introduces a separation of functionalities. The client, or front end, is responsible for presenting the data and doing some processing. The server, or back end, is responsible for storing, protecting, and performing the bulk of the data processing.

With its tools that assist in the rapid development of queries, forms, and reports, Access provides an excellent front end for the presentation of back-end data.

For years, most information professionals worked with traditional programming languages to process and maintain data integrity in the application. With traditional programming languages, data-validation rules were embedded in the programming code. Furthermore, these types of applications are record oriented—that is, all records are read into memory and processed. This scenario has several drawbacks:

  • If the underlying data structure changes, every application that uses the data structure must be changed.

  • Data-validation rules must be placed in every application that accesses a data table.

  • Presentation, processing, and storage are handled by one program.

  • Record-oriented processing results in an extraordinary amount of unnecessary network traffic.

  • + Share This
  • 🔖 Save To Your Account