12

MS Access and VBA.

This combo is the worst dev tech I had to use it by now. Why? Because even if you try it, you can't make a single line of clean code. The syntax is horrible, it still use GOTO...

Maybe the reason why I hated working with it is linked to the context too: I was (and still) developing a system using NoSQL database and this system should be mostly fully configurable through metadata within JSON documents and it was. But we were still writing every JSON by hands so we decided we needed to develop a web based utility for us and clients who would need to configure the system but one of the head decision making people said that we don't need to use fancy technologies (because NoSQL is already "fancy") and that the configuration tool will be develop with Access because he used it a lot when he was younger and when he was coding during its free time. He said that using Access would be much easier and much time saving than our "fancy web based solution" and that he could help if we had questions...

Developing a MS Access software is already a pain in the ass but when you need to output JSON with it...

Comments
  • 1
    I don't understand why people would ever use access in production... Demo use sure why the hell not. But in production it's nothing but a headache to develop and even worse in response and request. Had an application at work that used access (3rd party) with an option to connect to SQL. User complained it was being slow. I immediately upgraded him to the latest version and moved it all to SQL. Problem solved and never to have an issue again.
Add Comment