What NOT to write on your resume
We've been hiring here at Blue Cross as we tend to do. This time it's for a position on my team. Given the high volume of talented people out there, I was looking forward to reading their resumes. Being the naive guy I am, I forgot about one thing: bullshit. Yes, it's out there. It's out there on a lot of resumes. In fact, sometimes you can't even detect it until the candidate comes in for an interview. Then it takes on a more amusing verbal form and you're stuck there for the full hour until it's over.
Some people on the other hand are quite talented. In fact, they can do things with Access that even Access can't do. Well, maybe because their version of Access uses a "company engine". Sounds special. I wish I had a special "company engine" for my Access installation. We're stuck with the Jet database engine. For those of you unfamiliar with MS Access, it's just a database itself. In fact, the database portion of it is the Jet database engine. The rest consists of frontend functionality built on top of it. This results in an all inclusive product that handles relational backend data storage with frontend development such as forms and reports. Not a bad combination. In fact, it's a very useful, easy to use, quick and dirty way to get things done for many businesses. Granted, once you go beyond a rather small threshold Access is no longer a viable solution. Hell, it's VBA doesn't even support try/catch blocks. The shame. But I digress.
"Work on projects to add multithreaded capabilities to company engines in MS Access."
Per a Microsoft forum moderator:
So unfortunately, if you want to use multiple threads in Vba for any Office application (i.e. Access), you are more or less out of luck. There is no support for this in the respective Vba integrations. I suppose if you really had to make this work, you might be able to call the Win32 apis directly from Vba (and/or write a dll to give you the support you needed).