You could try microsoft.public.access.dataaccesspages, as Kevin suggests
elsewhere in this thread. However, unless the situation has changed
dramatically since the last time I checked out that newsgroup, I'm afraid
you'll find that many questions there go unanswered. I don't know of any
experienced Access developer who works with DAPs. (I think I may have said
in another recent thread that I knew of one, but on reflection, that person
is primarily an author and trainer rather than a practicing developer.)
DAPs are very restricted (they require the Office Web Controls and work only
with recent versions of Internet Explorer) and require the developer to
learn techniques that are very different from anything else in Access. If
you have to learn new techniques, why choose something so restricted,
instead of ASP or ASP.NET, which create pages that will run on just about
any computer with a browser and an Internet or intranet connection?
