I have done A LOT of ADP work in the past and It is intended as a Client Side in a Client/Server enviroment (You will need a copy at each client but that is the easy part). It works very well if you know what feature to use for what task and in my opinion ADP represents an extremely flexible reporting interface with MS ACCESS Goodies
HTH
I've been working with ADP for 2 years now (I tranfered an old access 97 mdb to sql server). The application is installed on more than 50 desktop and is used as the main application in the company (access runtime is used to run the adp)
I have to say access (2002) adp is an excellent way of creating a cheap and fast SQL Server front-end. Of course you don't have the flexibility of VB, but I've been able to do anything the company needed with an access ADP.
Tip : DON'T share the adp over the network!
Back when I did lots of Access/SQL apps I kept a copy of the MDB file in place on the network. At this company, there were about 50 users. We added a line in the login script to copy that file to the workstations so that it was always up to date.
To update each computer, I created a proc to update the database. It is pretty simple :
1) Create a global variable in your project which contain the version number of the project (the one installed on the computer)
2) In a parameter table, create a line which contain the most recent version of the project (I update this field manually whenever I make a new version)
3) When your project loads, compare 1 and 2. If 1 < 2, I close the database and runs a batch that copies the project from the network to the user's computer
This way you don't cause an overload on the network each morning and you can keep track of your version changes...
