Hi Philip,
With proper design, you should be able to create a solid multiuser Access
application that can easily support 40 to 50 simultaneous users. The golden
rule is to fetch only the data that a user needs. I have a new tutorial paper
available on the Seattle Access User Group, for a presentation that I gave a
few weeks ago. See the download, available here:
http://www.seattleaccess.org/downloads.htm
Query By Form - Multi Select
Tom Wickerath, February 12, 2008
Download (269kb) Using Multi-Select Options; Word doc and mdb
I will eventually convert this to a web page on my new web site, as time
permits. Make sure to follow all of the recommendations in my Multi-User
Applications write-up. This is a compilation of many years of learning the
hard way. For example, disable Name Autocorrect, set all table subdatasheets
to [None] (you must disable Name Autocorrect first, to get the table
subdatasheets setting to "stick"), establish a persistent connection, use
proper indexes, and use the JETShowPlan registry setting to ensure that you
are not causing any table scans for tables with a large number of records.
For small tables, the query optimizer may very well decide that a full table
scan is the most efficient query. I wouldn't worry too much about tables with
a small number of records, like say 50 or less.
Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________