8
rooHype
5y

Programming excel macros is the worst thing one could do to himself. VBA is the most cancerous anderen inconsistent language I had the "pleasure" to work with. I have problems like the following all the time for no apparent reason. For example: you script something, test is and everything is working just fine and dandy. Next day when you run the script, guess what...i doesnt work anymore. For no apparent reason what so ever. Maybe its just me, but i just want to hang myself working with it.
Anyone else has had such "Love story" like mine?

Comments
  • 1
    Good friend of mine got stuck maintaining a legacy VBA application and has similar views. Personally I run a mile from any role that even mentions it!

    Good luck.
  • 1
    My condolecense for your friend. I really am glad that this is a new project, i cant even fetch how bad a legacy version will be. And I can only recommend staying away from it.

    Although i have to admit: when it works it can be very useful!
  • 0
    To add to the pain, it gets even worse when using _localized_ VBA(!)

    Im not kidding, VBA got translated into, amongst others, Swedish and we were supposed to write "Om Inte x < 100" ... ( If Not x < 100 ... )

    Now I havent used VBA for many years and things might have changed, but this was true atleast when VB6 was around...
  • 0
    Well luckily i'm not that deep into VBA development. But it still sounds horrible
  • 0
    never had these issues with macros, at least in Word/Powerpoint. Then again, I write PoC malware for fun, but still...
  • 1
    @Parzi you got to love it or hate it i guess. The more you work with it the less buggy the macro gets (or so the theory)
Add Comment