I have been using Access Data Projects for several years now.  IMHO, it is about the fastest and most efficient method of doing client-server SQL Server applications that can scale to literally hundreds of concurrent users (yes using Access as the client, but just for the GUI and the excellent report writer of course).  I would not consider using ODBC DSNs etc. as this article suggests.  I am surprised that Microsoft and the development community generally has missed the boat on this marvellous technology combination.  My apps are lightening fast and the users love their responsiveness, performance and functionality. 

It is truly a "rich user experience" that everyone wants in their systems.  I even have one application - no bound controls, all forms and controls populated in ADO code using stored procedures, of course, as the back-end retrieval mechanism - that was able to run 10 concurrent users quite satifactorily over a 56Kbps communication line between the East and West coasts.  None of our other Corporate applications (except for web applications of course) would work over that line.  Anyone who wants to use Access as the GUI for the ease of development and the best-of-breed report writer that everyone is trying to emulate lately, should check out ADP technology.  It is that, or use VS 2005 and .Net 2, in terms of speed of development and developer-friendly technology that results in efficient, scalable apps and a "rich user experience".