no, i really don't have another suggestion.
adp programming requires ADO which is more involved than DAO. ODBC
connections are really very easy.
ADPs aren't getting as much attention from the Access team, so I don't
recommend building new systems using them.
Dave's right, ODBC connections are easy to manage, especially
DSN-less. There's lots of example code available online. And we
often find reasons to link to local JET/ACE tables for work tables,
merges, imports, etc.
I've written a slideshow on techniques for using Access as a
client-server front-end to SQL Server databases. It's called "Best of
Both Worlds" at
www.JStreetTech.com/Downloads. It includes some
thoughts on when to use SQL Server, performance and security
considerations, concurrency approaches, and techniques to help
everything run smoothly. It focuses on using MDB/ACCDB instead of
ADP. We've built many systems using these techniques.
Armen Stein
Microsoft Access MVP
www.JStreetTech.com