this post was submitted on 16 Feb 2025
65 points (98.5% liked)
ADHD
10144 readers
183 users here now
A casual community for people with ADHD
Values:
Acceptance, Openness, Understanding, Equality, Reciprocity.
Rules:
- No abusive, derogatory, or offensive post/comments.
- No porn, gore, spam, or advertisements allowed.
- Do not request for donations.
- Do not link to other social media or paywalled content.
- Do not gatekeep or diagnose.
- Mark NSFW content accordingly.
- No racism, homophobia, sexism, ableism, or ageism.
- Respectful venting, including dealing with oppressive neurotypical culture, is okay.
- Discussing other neurological problems like autism, anxiety, ptsd, and brain injury are allowed.
- Discussions regarding medication are allowed as long as you are describing your own situation and not telling others what to do (only qualified medical practitioners can prescribe medication).
Encouraged:
- Funny memes.
- Welcoming and accepting attitudes.
- Questions on confusing situations.
- Seeking and sharing support.
- Engagement in our values.
Relevant Lemmy communities:
lemmy.world/c/adhd will happily promote other ND communities as long as said communities demonstrate that they share our values.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What's the advantage of VBA in this use case over other options?
They said they barely know vba. So it's probably the integration into MS tools.
So I had tried using the data import wizard or whatever it was that's built in to pull an entire folder into the workbook, but I had roughly 70 workbooks, all with 40 columns and anywhere from 3,000 to 20,000 rows. At the end of it all, I probably had over 20 million cells. The built-in tool was being finicky. I think it was that the sheer amount of data I was working with was too much for it to handle. But it kept giving me errors about formatting.
So I gave up on it, and I spent several hours of my life reading manuals and forum posts on how best to achieve one step and testing code on backups. It was truly an all-day thing. But when you're dealing with dozens of files, this macro takes maybe 45 seconds to do its thing whereas the manual process could waste an hour of your day. And I plan to share it with the team once I get it a bit more polished because it's not exactly where I want it. But I think the rest of my colleagues will love it.
I know a little VBA. I spent a whole weekend writing a macro because I did my personal budgets in Excel, and I wanted to automate some stuff because I could conceptualize how it could be done. I don't use Windows at home anymore so I want to figure out how to bring it over to LibreOffice Basic. Still, since the business world uses Microsoft products, knowing VBA is a much more marketable skill so it is useful to practice in VBA whenever I can.