Wrox Programmer Forums
BOOK: Access 2010 VBA Programmer's Reference
This is the forum to discuss the Wrox book Access 2010 Programmer's Reference by Teresa Hennig, Rob Cooper, Geoffrey L. Griffith, Jerry Dennison; ISBN: 978-0-470-59166-6
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Access 2010 VBA Programmer's Reference section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old October 2nd, 2011, 10:06 AM
MDB MDB is offline
Registered User
Join Date: Sep 2011
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default ADP Limitations


I have recently started working at a place that heavily utilize ADP Access projects. The programmers reference book suggests that SQL Server shopuld be used for systems greater than 2 GB and with more than 20 users. It also suggests that ADP's may be used as a solution.

At my current work they have a system written usinmg ADP which is 4gb in size with maybe 30 users. They are concerned that Access cannot handle large amounts of data and are concerned that this critical application may die (even though this is written using ADP and unbound forms). Are the concerns valid?

What are the limitations of ADP projects (e.g. number of users and soize of databas).

Is there anything I should check in the system to see if things are done properly to cater for larger systems (the vook says to utilize record sets).

Old October 11th, 2011, 02:27 PM
gjgriffith's Avatar
Wrox Author
Join Date: Jul 2009
Posts: 110
Thanks: 5
Thanked 14 Times in 14 Posts
Smile ADP Specifications/Limitations

Hello MDB,

Thank you so much for reading the Access 2010 programmer's reference and for posting your questions about ADPs! I'm so sorry it has taken me so long to get back to you about this, I'm just seeing it now, but hopefully I can help out here!

In general, limitations for ADP data connections and users are specific to SQL Server (because the ADP is just using ADO under the covers to access the data on the SQL Server) and what you are saying here is correct. The Microsoft Access team provides a bunch of information about ADPs and their limitations at:
Under the section about half way down on the page, titled "Microsoft Access project specifications", but this doesn't really talk about the number of users, again, because this is dependent upon SQL server.

In general, the recommendation is that every user use a separate copy of the ADP to connect to the SQL server (i.e. not 50 users accessing the same ADP file simultaneously...each user should have a separate copy of the same, or different, ADP file to run the application) and in theory, you should be able to have thousands of users working with the data simultaneously. Does this make sense?

Anyway, I hope this helps answer your questions about ADPs in the multi-user environment, but if you have other questions about this, please let me know and I'll do what I can to help!

Geoffrey L. Griffith

Wrox Author of:
Microsoft Access 2010 24-Hour Trainer
Access 2010 Programmer's Reference
Access 2007 VBA Programmer's Reference

*** Please click the THANKS button (to the right) if this post helped you! *** ---------------------------------------------------------------------------------------------------------->

Similar Threads
Thread Thread Starter Forum Replies Last Post
AJAX limitations rajesh_css Ajax 1 April 29th, 2009 07:08 AM
Database Limitations rfurman1161 Access 2 April 5th, 2006 01:45 AM
Limitations of Replace philstaite BOOK: Beginning ASP 3.0 5 September 10th, 2004 10:07 AM
Limitations of Replace philstaite ASP.NET 1.0 and 1.1 Basics 6 September 8th, 2004 01:16 PM
MSAccess Limitations if any happygv Access 5 April 19th, 2004 08:45 PM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.