The multi-user characterisation by Microsoft for A97 was done
for 32 users.  The biggest problems with having a large number
of users have to do with organising the back-up, maintenance
and roll-over systems: what will you do if your file becomes
corrupted? what will you do if your server goes down?

By using TS, you avoid problems with network optimisations,
but you will still have latency problems caused by the Jet
data cache, and you now run multiple copies of Access on one
server. I would have thought that you would start to run out
of memory soon - if not a 20 users, then perhaps at 40.

(david)

A97 may not do that well on Terminal Servers.  At least according to
the admins at a client of mine.    This is very likely related to the
keyboard and mouse event polling as indicated in the following KB
article.

ACC: Microsoft Access Shows 100% CPU Utilization During Idle Time  
http://support.microsoft.com/?kbid=160819

YMMV of course.

The number of users 20-25 is more of a factor of how stable the
hardware is.   If you are using TS system then clearly you have many
fewer factors.

That said a client still had some problems with one particular server
in a cluster of four Citrix servers.  Once the admins changed the
balancing settings from utilizing that server for that app things were
much better.

Tony
--
Tony Toews, Microsoft Access MVP
  Please respond only in the newsgroups so that others can
read the entire thread of messages.
  Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

I have multiple companies running with around 50 users on Terminal Services
on Access 2000/2002/2003 for a number of years now without any major
problems at all. The speed of our systems are much improved by on running on
a Terminal Server as opposed to a normal client and fileserver situation.
Ensuring there is enough memory on the server is a factor with around 3GB
for the 50 users.

I have no experience with Access 97 but know that 2000, 2002 and 2003 work
just fine.