Access ADP - For/Against?
Posted
by webworm
on Stack Overflow
See other posts from Stack Overflow
or by webworm
Published on 2010-05-03T19:39:33Z
Indexed on
2010/05/03
19:58 UTC
Read the original article
Hit count: 356
I have been tasked with taking an Access 97 application and moving the back-end data to SQL Server while moving the front end to Access 2003 (using Access Data Projects). In the process of this migration the back-end data structures will be changed significantly to support new functionality.
If I had my wish we would not be using Access as the front end. I think our application would be much better served by WinForms, WPF, or a web application. We have the time needed to properly plan a business logic layer and implement an excellent solution but powers above me want to stay with Access because that is what they are familiar with.
What I could use help with is pros/cons of continuing down this path of Access development. What are some legitimate arguments for and against using Access 2003? Here is what I have come up with so far.
Pro Access:
- Already own Access 2003 licenses
- Easy GUI development
- Reports look nice
Against Access
- Having to use VBA (Visual Basic for Applications)
- ADO vs DAO. Didn't Microsoft change things from Access 2002 to Access 2003?
- Not tied to Access runtime
- Choice in front end (WPF, WinForms, even ASP.NET)
- Maintainability
- True separation of logic from UI not possible
- Does Microsoft still support Access ADP?
Perhaps there are other issues I am not aware off both for and against Access for application development. I am trying to keep an open mind while at the same time trying to maintain my sanity.
I have been using C# since .NET was released and the thought of going back to VBA for six months makes my head hurt. Especially when I feel I could offer so much more if allowed to develop with modern languages and tools?
© Stack Overflow or respective owner