Is this a client-server application (that is, Access client, and a server DB
such as Microsoft SQL Server) or a multi-user Access/Jet application with a
split database but the tables in an MDB which is in a shared folder on a
server?
Unless there are some serious design and implementation flaws, it is likely
that either will handily support 30 concurrent users. I have worked on
client-server (Access client, Informix DB) with a user audienced in the low
hundreds, accessing the server DB over a WAN. And, we've had reliable
reports of Access-Jet multiuser environments where "everything was just
about perfect" supporting over 100 concurrent users.
But, no, I haven't had any experience with automated testing tools of the
kind you describe.
Larry Linson
Microsoft Access MVP
"Performer" <la************@eds.comwrote in message
news:11**********************@m73g2000cwd.googlegr oups.com...
>I need to test that an application using MS Access as the front end can
support up to 30 concurrent users. The front end is MS Access on the
client machine running Windows XP and the database is on a server. Does
anyone know of a testing tool that will work with MS Access to automate
recorded scripts and ramp up to 30 plus concurrent users?
