Chapter 36: Client/Server Concepts
1197
Cross-Reference
Table relationships are covered in Chapter 3.
Access as an Internet database
Although an Access database can be used to drive an Internet site, this practice is not recom-
mended. The Access Database Engine just can’t hold up to hundreds of simultaneous requests,
particularly when data is being modified in the database. Performance is sure to suffer, and data-
base corruption is virtually guaranteed in such an environment. For any measure of scalability,
something like SQL Server is best. And SharePoint is increasingly a viable data repository for
Access applications, or, at the very least, portions of the data provided by an Access application.
Using SharePoint Services and Access in tandem might allow adequate servicing of a small-scale
Internet database, or perhaps a localized company or educational intranet.Summary
This chapter has provided the basis for understanding the differences between an Access desktop
application and a full-blown client/server database produced with a database engine such as
SQL Server. Access is a fine development tool for producing client-side user interfaces to server-
provided data. Access’s excellent report writer, its superior forms designer, and VBA code combine
to produce powerful and useful front ends for SQL Server data.The user is unaware whether the data in an Access form or report resides on his desktop computer,
on the local network, or across the Internet. This level of remote data integration wasn’t practical
with older Access databases, but it’s been made possible by the features built into recent versions
of Microsoft Access.