I too have been struggling as to which way to go. I've done several DAP beginning with Access 2000 and now 2003. Access 2003 is certainly much better. The script editor is not that great. It gets confused when you go outside of what Access is expecting. Consequently, I've been using FrontPage for some of my editing.
I've not developed ASP pages, but some of my coworkers have. And I'm not impressed. Mainly because I don't like having the user fill in a form and then press the submit button, only to find some of the answers are incorrect. I prefer checking the value the user enters immediately after they leave the field. And DAP provides this functionality (i.e. client-side scripting). It seems to me that one would have to jump through quite a few hoops to program ASP pages to validate user entry as they leave the field rather then after the submit button is pressed.
I'm speculating, but to fill in the fields on an ASP page from data from a table, one would have to write the code to do so. Likewise, to save the data from a form to a table, again, one would have to write the code to do it. Why bother when DAPs does this for you plus handles quite a few addition events?
So far, DAPs have not prevented me from doing what I want. I use DAP to handle the connections to the db and fields on my form. I use FrontPage to do things that it does better than Access, and vice-a-versa.
I guess I'm going to stick with DAPs until someone can show me the I can do client-side scripting (that is validate user entry as soon as the field looses) with ASP just as easily.