There can be only one... Microsoft Excel Champion Channel surfers seeking refuge from the world might have stumbled across an esport on ESPN2 that is as brilliant as it is horrifying. Ladies and gentlemen, we give you the Excel Esports All-Star Battle. It has a been a rocky road for competitive video gaming on the sports network. In 2016, ESPN embraced the esports phenomenon …
One more example, we fear, of people trying to make Excel do something that it really can't.
The trouble is that as a desktop application with features including data access connectors, an expressions syntax and a (sort of) programming language available to users Excel can do anything; it's just that in the majority of cases it shouldn't.
As I'm fond of saying: you can build a fully functioning game of Tetris in an Excel workbook, but if you want to actually play Tetris you should pick up a Game Boy.
Anyway, I can only assume that I'd automatically win the Excel playoffs by just creating a small database. Data types! Ref integrity! The ability to distinguish between a 0, an empty string, no data and a failed lookup! They wouldn't know what'd hit them.
I worked with someone who tried to do everything in Excel. Office layout? Simply make all the cells square, representing a 10cm square of the office plan. Then colour in the cells as appropriate. Powerpoint presentation? Use worksheets as separate slides. It was simultaneously impressive and awful to watch.
Excel hasn't quite got to the point where you could compile Excel from Excel.
Now that I've said that: With some dirty VBA backend you probably could use Excel as a macro Assembler; with some dirty VB backend to turn the macro into functioning binary.
Ye gods what twisted idea have I set someone loose with...
I'd be interested less in speed of usage, and more about just how far folks can take the VBA. My usage of it in Access goes way beyond anything Access was origamally designed for, though it's getting threatened now that employers (i.e., my current one) are starting to feel that VBA's Win32 API capability is a 'risk too far' and are blocking it using the Virus Scanner when in an Excel file.
Mere fast and flashy fluff for the macro and formula kiddies.
For the connoiseur of a true sporting contest, there is the 5 day Active Directory administrator test match, where 2 teams of AD sysadmins with full administrator rights compete to get each other "out" by restricting the other team's access to a series of hellishly complex corporate server and PC networks, with "runs" scored when a team manages to perform a simple business task without any fine grained permissions stopping them.
User inability to conceptualise relational databases is the main reason, or their desire to treat every problem as the nail matching the hammer they've mastered. Hence the resourceful person who haunted user forums in the 90s with the relational database they built with Word tables and WordBASIC.
Users mostly want tables with some cleverness, hence so many focused tools for table management.
Access is looking almost like abandonware now:
New features added to Access 2021:
- Slightly improved add tables task pane
- Slightly improved tabs for table view
- Slightly improved linked table manager
- New DateTime2 format with greater range and precision
- Support for Dark Themes
- Slightly improved query designer
- Slightly improved relationships window
- Slightly improved colour picker dialogue
I got deeply into Access 2.0 in the mid 90's, and did some fun, whizzy things with it for my easily-pleased PHB at the time. But it seemed to me then that its limitations in the workplace meant that it would never stay the course like Word & Excel.
Fast-forward 25 years, and I'm now slowly shaking my head in despair that it's still being kept alive. Is it the right tool for any job? Who actually uses it, really?
Access is built on top of the (DOS era) database primitives provided by the file system. There was a move to update the record handling primitives, which would have naturally led to a new version of Access, but the project was canceled. There was also Access 2000, which could live in SQL Server 7 --- but that was killed by SQL Server 2000 a few months later, which dropped the API used by Access 2000 for project storage.
So both the new directions for Access were killed.
The modern equivalent for Access is Web applications, with a Web Server and Database server. The web page description is very similar to an Acess/VB6 form description. Access never got into this area because ... VBA in browsers was killed, HTA's were killed, JET back-ends were killed, and Access front-ends were killed.
It's unfortunate because, although a web server and database is standard for development now, it's still a step larger than having that API built into the workstation operating system. What may be on the horizon now is having that API available in the Browser. You can get a web server operating in a web browser now, but the whole 'sandbox' thing is the enemy of persistent shared storage. Still, that's where I see an Access replacement might come from.
The problem I have, and I don't think it's that uncommon, is that I currently work on the 'business' side of the I.T. 'wall'. I.T. won't give business-side developers servers with a database and web server installed. They want to control it themselves, provide it in a data center as far away and cheaply as possible, yet still charge an exhorbitantly high price for an inferior, difficult-to-get-changes-made, end result.
With that in mind, I can develop solutions using Access far more quickly, far more cheaply, and far more responsively. However, Access's 1990s interface, its network hogging, its low security, etc, are all serious limitations that are difficult if not impossible to work around.
What I'd really like to be able to have is a server on site, with a suitable database system for the tasks at hand, and a web server installed, and be able to do all the work locally. That way I can get my work done and users aren't limited to Access on the desktop as the only way to use the apps.
I reckoned they should have built an easy-to-use frontend for an installation of SQL Server Express Edition and then retired Access gracefully.
It should be something that builds reports & databases with the ease of Access and something that does not require an installation of Management Studio.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
