mid.gif (2241 bytes)
FormMenuStart.gif (2069 bytes) FormMenuEnd.gif (441 bytes)
Knowledgebase Article 260

We currently run another defect tracking system on MS Access. It is clear from our experience and Microsoft's own admission that Access can not reliably support more than 8-10 simultaneous users. The MS Access spec says that it can support a max of 250 users. Yet your pricing structure goes to 250+.

If Microsoft's own spec says that 250 is the maximum number of Access users (and reality says that 8-10 is the maximum) how can PR-Tracker reliably (or even theoretically) support as many users as are shown on the price list?


tWe have been aware of Access problems since the inception of PR-Tracker and have worked around it. PR-Tracker actually supports up to 2000 users, however, our largest customer only has 400 users. The design approach that we took to work around Access limitations is documented below.

(1) When PR-Tracker is open, it doesn't stay connected to the database. It only connects to the database to perform an operation and then it disconnects. Most transactions and queries take less than a second. If you have thousands of problems in a project a text search query may take 3 or 4 seconds. Generally speaking, a person could have PR-Tracker open all day long and spend less than a minute of time being connected to the database.

(2) Each project is stored in its own .MDB file. So what matters is how many people are connected to a PR-Tracker project database -- not how many people are connected to the PR-Tracker database.

(3) PR-Tracker stores data redundantly. It is stored in the .MDB file and the .PR files. When you are viewing a problem report, PR-Tracker gets the data from the .PR file instead of the .MDB file. This makes the operation a little faster and reduces the number of times PR-Tracker connects to the project database.

NOTE: PR-Tracker 5.10 and above supports both Access 2000 and SQL Server
CornerLeft.gif (244 bytes) CornerRight.gif (244 bytes)


endln.gif (223 bytes)
Nine tips for effective bug tracking | Home | Site Map | Search Knowledgebase