"Nick 'The Database Guy'" wrote
Quote:
Originally Posted by
Think is that I would have my doubts
about using an access application
with a front end application that can
have potentially unlimited users.
>
Access can only handle, at the very most
(and I am open to correction
if anybody has other opinions) 20 users.
There is no such limitation in Access/Jet -- the physical limitation is 255
concurrent users, but not many people will contend that you can actually
support 255 users. However, there are many reports of significantly more
than 20 concurrent users. How many users can be supported with good response
and performance depends on a number of factors, and the factors are
different if you are using a Jet database with .asp code, as this poster
described.
Depending on the way the website is coded, it is possible that no matter how
many people are using the website, there will only be a single user of the
Jet database (see other threads, re: Access vs. Jet -- you are using a Jet
database). If you expect heavy traffic, and many people to be using your
site concurrently, I'd suggest you use a server DB, instead of Access, but
if it will only have a modest number (in the tens, say) of concurrent users,
Access may serve your purposes.
If I were doing in Access what you describe, there'd be multiple Queries,
with one or more being data source for the final Query. As you will be, no
doubt, want one Query with subqueries, I'll leave that exercise to someone
else who enjoys writing SQL from scratch.
Or as an alternative, get a copy of Access, build your basic Queries in the
Query Builder, and copy/merge the SQL.
Larry Linson
Microsoft Access MVP