It is common to configure web servers so that they log
in a only ONE user, rather than requiring each separate
user of the web page to log in to the Windows Server.
It is common to configure web servers so that they use
a pool of connections for all web users, rather than
creating a new connection for each web user. That is,
they have a pool of connections for the ONE database
user, which are shared among all web page users.
It is possible to configure an Access connections so
that there are an infinite number of possible read-only
connections, but generally it is considered that having
an infinite number of database users does not scale as
well as having just ONE database user with a pool of
connections.
Individual records in an Access database are limited
to 2GB: in practice most designs would be for a total
database size less than 2GB because of feature limitation
at that size: in practice most practical use would be
for a total database size less than 200MB because of
design optimisations for smaller sizes.
Use of Access with IIS is not supported by MS. Most
of what is written about this is the most ridiculous
nonsense, but it does seem that IIS has had problems
with the multi-threaded nature of the Jet Database
Engine. If you are bent on using Jet with a large
number of web users, you should consider setting the
number of threads for Jet to 1.
Use of Access with IIS often presents problems with
backup, update, or modification. For these reasons,
use of Access is often rather more work than it first
appears.
(david)
