Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I was recently asked to update an old Access Forms application. Coming from a .NET background, I found the change frightening, and became somewhat uncomfortable. I had assumed these were legacy technologies, fast becoming anachronisms…
Am I wrong? If so, what are the reasons to continue using this technology (besides avoiding the cost to port old apps to .NET)?
There is still a ton of software written in COBOL, and that’s much older than Access.
There are some areas where an Access application is probably sufficient and the least expensive option. If it gets the job done (your job is partially to let your employer know if it really gets the job done) and if it’s what they want, go for it.
If you see good reasons that a .NET project would be better or that Access will fall short, discuss them openly and try to reach a decision that’s in the best interest of the person cutting the check.