Benefits to development in MSAccess before JSP

I am looking for input of why it might be beneficial to build a prototype in MSAccess for users first instead of JSP.  To develop in MSAccess and later build in JSP.
Thanks in Advance.
Who is Participating?
Can't imagine why you would do this.
Seems like a bizarre choice to me given that the technologies have nothing in common.

To me, the only possible reason would be to mock up form or report layouts for user approval but you could use any number of non-programming tools for that.

It's just my view of course.
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Pretty much ditto what Peter said.  The two technologies are pretty much unrelated.

But ... as noted, a mockup might be of use.  

Jeffrey CoachmanMIS LiasonCommented:
The kicker here is that if you are not that good at Access development, it may be a bit of a waste of your time and resources.

Besides, you have not posted any of the details on this project.
There are just to many parameters involved that we don't know about.

Perhaps you can first take a step back and fill in some of the blanks...?

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.