Getting ptsd flashbacks from having to work with access.
Database corruption was so common I’ve had scripts in place to run automatic recoveries.
Terrible security, performance, and SQL feature support.
I’m so glad that thing is buried deep where it belongs
Access let you build visual apps, usually data-entry workflows, around its internal SQL database. You could build small apps with it using Visual Basic and a visual UI editor. Plus, all your work ships as a single file, provided the user also has Access installed. In many ways, it was like Apple’s Hypercard, but also way easier to write than webpages with the same capability. Oh, and you don’t need a server anywhere to make it work; it’s 100% local. It was also the next logical step to take after the most complex things you can do in Excel.
That said, it was crippled from the start - still very useful, but not for heavyweight stuff. It’s limited to a fixed number of UI, pages, database rows, etc, so it wouldn’t compete with more expensive MS solutions (this thing came with Office). I don’t think it got a lot of love because of that, but I personally used it to solve some real problems in the workplace, without need of any (official) developer resources.
In the present day, it would actually compete with a lot of simple business cases that are served in the cloud at some cost.
Outlook 2000 was magic, even if it had more security warnings than a trip to Yemen. The current iteration of Outlook that they’re pushing with Office 365 is an absolute disaster, as if they’ve dragged it down to Teams’ level and let it rot away.
The seven horsemen of the 90s workplace computer apocalypse.
Alas, Access was too powerful to make the transition to the cloud. It couldn’t be allowed to survive.
Getting ptsd flashbacks from having to work with access.
Database corruption was so common I’ve had scripts in place to run automatic recoveries.
Terrible security, performance, and SQL feature support.
I’m so glad that thing is buried deep where it belongs
Access got FoxPro’d, right in the kisser
What does it do again?
It’s what many should have used instead of doing everything in gigantic macro filled Excel file.
Access let you build visual apps, usually data-entry workflows, around its internal SQL database. You could build small apps with it using Visual Basic and a visual UI editor. Plus, all your work ships as a single file, provided the user also has Access installed. In many ways, it was like Apple’s Hypercard, but also way easier to write than webpages with the same capability. Oh, and you don’t need a server anywhere to make it work; it’s 100% local. It was also the next logical step to take after the most complex things you can do in Excel.
That said, it was crippled from the start - still very useful, but not for heavyweight stuff. It’s limited to a fixed number of UI, pages, database rows, etc, so it wouldn’t compete with more expensive MS solutions (this thing came with Office). I don’t think it got a lot of love because of that, but I personally used it to solve some real problems in the workplace, without need of any (official) developer resources.
In the present day, it would actually compete with a lot of simple business cases that are served in the cloud at some cost.
No one truly knows, but there’s always that one guy in the office using it for god awful things it was never meant to do…
I’m still pissed off that they dropped the gold(ish) colour for Outlook.
Outlook 2000 was magic, even if it had more security warnings than a trip to Yemen. The current iteration of Outlook that they’re pushing with Office 365 is an absolute disaster, as if they’ve dragged it down to Teams’ level and let it rot away.
As you can tell, I’m not a fan.
I’m holding to old outlook for as long as I can. I’ll bitch and moan when they rip it out of my hands.