VB CreateObject..
Cuz it creates an ActiveX object..
I am using it to manipulate excel files..

Yeah, old code, finally getting around to replacing it, probably with something cross platform too.

But in the meantime, I still have to fix remaining bugs or add small features.. Lately just the latter. I manage to do so, even though it takes a lot more time that I'd like to admit as I'm not coding with VB on daily or even monthly basis...so the goddamn ; are everywhere, fucking with me like I killed the pope..
And the code is horendous.. I'm not even sure if it can be done more elegantly, with lesser lines etc.. but to me it feels like I am powertaping a stick to a robot and hoping it will autoconnect and start functioning as a third arm joined with using electric screwdriver to disassemble a watch..

  • 1
    Just use enough duct tape and it will solve any problem :P
  • 0
    @Voxera Well if applied to customers, it definitely will!! 🤣🤣🤣🤣😇
    Not related to original rant content, but sometimes they suggest how we should implement something & it's like the worst case possible.. worse would be only to do everything on paper & manually insert data to the db...
  • 1
    @sladuled if that means that data in the db is correct I can see many worse solutions :)

    But manual entering, no that should definitely be a last resort.
Add Comment